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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds only the 'recent' temporal scoping, which is a modest behavioral detail, but it does not disclose output format, pagination behavior, or rate-limit implications. With annotations doing most of the safety disclosure, a 3 is appropriate.

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 concise sentence with no filler or redundancy. It is front-loaded with the verb and resource, making it easy for an agent to parse quickly.

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?

There is no output schema, so the description should ideally clarify return shape beyond 'tweets'. The schema's text_only parameter hints at tweet fields, but full output format and recency bounds are unspecified. Still, with well-documented parameters and clear safety annotations, the tool is callable without major guesswork.

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 input schema fully documents handle, count, cursor, and especially text_only with rich conditional guidance. The tool description itself adds no parameter semantics beyond what the schema provides, which matches the baseline of 3 for fully covered schemas.

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 the action ('Get') and the resource ('recent tweets from a specific X/Twitter user'), which is unambiguous for an agent selecting a user-timeline tool. It does not explicitly differentiate from siblings like twitter-read or twitter-search, so it loses the top score, but the purpose is still clear.

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 the tool is for retrieving a specific user's recent tweets, giving a clear usage context. However, it does not mention when to prefer this over alternatives such as twitter-search, twitter-thread, or twitter-read, nor does it provide any exclusions. The text_only parameter has usage guidance, but that is parameter-level, not tool-selection guidance.

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