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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior, so the description's main added value is the data-quality caveat that posts are 'unverified claims, not news confirmation' — genuinely important for downstream reasoning. It adds nothing about rate limits or result freshness beyond the schema's hours field.

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?

Three sentences, zero filler, front-loaded with what the tool does before the routing condition and the reliability caveat. Every sentence earns its place.

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?

For a search tool with no output schema and no nested objects, the description covers purpose, routing, and a critical data-reliability warning. It falls short only on result shape and the two undocumented windowing/pagination parameters.

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 0%, so the description must carry all four parameters. It meaningfully explains 'query' (phrase, cashtag, handle, advanced syntax) and implies the 'queryType' enum via 'sorted by Latest or Top', but leaves 'hours' and 'limit' entirely undocumented in both schema and description.

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 the TWIT X feed') and enumerates the accepted query forms (phrase, cashtag, handle, advanced X query) plus sort modes. It differentiates itself functionally from cashtag-oriented siblings via the routing sentence, though it never names social.ticker_posts explicitly.

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?

Gives a clear when-to-use condition: 'Use when a company name or event is not captured by its cashtag,' which implicitly steers the agent away from ticker-scoped search. There is no explicit when-not-to-use or a named alternative, which keeps it short of a 5.

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