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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing this as a safe, non-mutating operation. The description adds no additional behavioral details beyond the word 'Read' and does not contradict the annotations. Missing extras like return format handling or rate limits mean it is neutral, not enhanced beyond annotations.

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, front-loaded sentence that says exactly what the tool does with no filler words or redundant details. Every word earns its place, making it an excellent example of concise and well-structured tool documentation.

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 the simplicity of the tool (2 parameters, no output schema) and strong annotations, the description is sufficient to guide invocation. It covers the core behavior and the schema handles parameter details. It would be a 5 if it explicitly mentioned the text_only option or response shape, but those are reasonably inferable from the schema, so 4 is appropriate.

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?

The input schema provides 100% description coverage for both parameters: 'tweet' is described as 'Tweet URL or tweet ID' and 'text_only' includes its purpose. The description's phrase 'by URL or ID' adds no new meaning beyond the schema's parameter description, so it earns the baseline score of 3 without extra contribution.

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 ('Read'), the resource ('a single tweet'), and the input method ('by URL or ID'). This distinguishes it from sibling tools like twitter-thread, twitter-search, or twitter-user-tweets, which operate on multiple tweets or different access patterns.

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 provides clear context for when to use this tool: when you have a specific tweet URL or ID and need to retrieve that single tweet. It does not explicitly mention alternatives or exclusions, but the phrasing implies its scope compared to siblings that handle threads, searches, or user timelines. This is clear context without explicit alternatives, fitting a 4.

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