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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint, idempotentHint=false). The description adds genuinely non-obvious context: no X developer account is required and calls are paid per call in USDC, which matters for cost-sensitive planning. It omits rate limits, pagination, and failure behavior, so it is not a 5.

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?

Front-loads purpose and the mode example, then the limit rule and payment note. The long enumeration of returned fields is justified because no output schema exists, though it makes the sentence dense.

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?

With no output schema, the description compensates by listing the returned tweet and author fields, and it covers modes, limits, auth requirements, and cost. Missing pagination and error/empty-result handling keeps it from a 5.

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 schema already documents mode, query, and limit semantics (including the clamping behavior for limit). The description echoes mode/query and the 1-20 limit range and adds a concrete example, but adds little beyond the schema, so the baseline 3 applies.

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+resource ('Tweets from X for one account or a search query') and separates the two operating modes. It doesn't explicitly differentiate itself from the sibling x-replies tool, which is the closest alternative, so it stops short of a 5.

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 clear mode-selection guidance (profile returns an account's tweets, search takes keywords) and bounds the limit to 1-20. It does not say when to prefer this over x-replies or what to do when a profile yields no results, so no exclusions are stated.

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