twitter_search_recent

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark this as read-only, idempotent, and open-world, so safety is covered. The description adds valuable context beyond annotations: it requires an API key (X_BEARER_TOKEN), limits the search to the last 7 days, and outlines the response structure, which significantly helps an agent anticipate behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured: one sentence states the purpose, a second block reveals the return format, and a final line covers authentication. Every sentence adds new information without redundancy, making it easy to scan and apply.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 10 parameters and no output schema, the description compensates well by explicitly showing the expected response structure (data, includes, meta), outlining the auth requirement, and giving a query example. This provides sufficient context for an agent to invoke the tool correctly and interpret results, even without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 10 parameters. The description provides a helpful example query and confirms the 7-day window, but it does not add semantic detail beyond that; the schema already offers thorough parameter descriptions. Baseline 3 is appropriate because most parameter meaning comes from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a clear action ('Search posts') with a defined scope ('from the last 7 days') and gives a concrete query example. This distinguishes it from sibling Twitter tools that fetch individual tweets, user timelines, or counts, making the tool's unique purpose explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies when to use it: when searching recent posts with query operators. It does not explicitly name alternative tools or state when not to use it, but the context is strong enough that an agent could infer appropriate usage, especially with the example query and time bound.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.