search_mentions

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

The description reveals ordering (newest first) but does not cover authentication, rate limits, or error behavior. With no annotations, more detail would be beneficial, but the core behavior is adequately stated.

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 a single sentence that front-loads the main purpose and includes key behavioral details (newest first) with no unnecessary words.

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 8 parameters and no output schema, the description is minimal. It covers core purpose and ordering but lacks details on response structure or pagination, which may be needed for effective use.

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 100%, so all parameters are already well-documented in the schema. The description adds no new meaning beyond summarizing that filters are optional.

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 clearly states it retrieves tweets mentioning a user handle, newest first, with optional filters. This distinguishes it from siblings like search_tweets (general keyword search) and search_community_tweets.

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 implies use when you need mentions of a specific user handle, but it does not explicitly state when not to use or contrast with alternatives like search_tweets. The context is clear but lacks exclusions.

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