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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: the result shape ({id, title, url}), the fetch follow-up path, and explicitly that the call is charged like tweet_advanced_search (Top ranking), which is important cost information.

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?

Four short sentences, front-loaded with the core purpose, then return shape/workflow, then syntax support, then cost. Every sentence adds distinct information with no padding.

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?

Given a single-param tool with an output schema (so return values needn't be explained) and annotations covering safety, the description covers syntax, cost, and workflow adequately. Minor gaps remain: what "recent" means and result limits/pagination are unspecified.

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 coverage is 0% for the single query parameter, so the description must carry it, and it does: it enumerates concrete X search syntax (from:handle, quoted phrases, lang:en, since:, min_faves:, -filter:replies). This meaningfully describes the accepted input format beyond the bare 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?

States a specific verb and resource ("Search recent public X (Twitter) posts"), which clearly separates it from user_search (users) and other user/list tools. It does not, however, fully differentiate from tweet_advanced_search, which it only references by name for pricing.

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?

Implies a workflow by telling the agent to "pass an id to fetch for the full text," routing to the fetch sibling. It also notes the charging model relative to tweet_advanced_search, but never states when to prefer this tool over that sibling or any when-not conditions.

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