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

With no annotations provided, the description carries the full burden and discloses nothing: no auth requirements, rate limits, result ordering, pagination, or empty-result behavior. "Search tweets" conveys no behavioral facts an agent could act on.

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 words with zero padding and the platform qualifier front-loaded, which is optimally compact. However, the brevity reflects under-specification rather than disciplined editing, keeping it short of a 5.

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 tool with no annotations and no output schema, the description should at least indicate what is returned, what the default `count` is, and whether `query` is optional. None of these are covered, leaving an agent to infer everything from the schema alone.

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 both `query` and `count` are already documented in the schema, and the baseline of 3 applies. The description mentions neither parameter and adds nothing (e.g., no query-syntax guidance).

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?

"X / Twitter: search tweets" expands the tool name into a platform-scoped statement but adds no distinguishing verb or resource detail beyond it. An agent cannot tell how this differs in scope from get_mentions or get_thread, which also retrieve 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?

No when-to-use, when-not-to-use, or alternative-routing guidance is offered. The siblings include get_mentions and get_thread, which overlap heavily with a tweet search, yet neither is referenced.

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