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

No annotations are provided, so the description carries the full burden, and it does well: it discloses $0.02 cost per call, the credit source, that failed/empty calls are free, and the return shape (up to 20 newest tweets with author, likes, retweets, views, URL). It omits rate limits or auth requirements, keeping it short of 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, then syntax, then output shape, then cost. Four dense clauses, each earning its place with no filler or repetition.

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?

No output schema exists, and the description compensates by naming the return fields; cost and failure semantics are also covered. For a single-param search tool this is essentially complete.

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?

With one parameter at 100% schema coverage the baseline is 3, but the description enumerates concrete advanced operators (from:user, "exact phrase", #hashtag, since:/until:, min_faves:, lang:) that meaningfully extend the schema's single terse example. Real added syntax value.

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: 'Live X/Twitter search'. The word 'Live' distinguishes it from the digest-style sibling x_digest, but it never names or contrasts with siblings like x_list, x_leads_deep, or x_digest explicitly. Clear purpose, weak sibling differentiation.

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 explicit when-to-use or when-not, and no routing to alternatives among the many x_* siblings (x_digest, x_list, x_profile, x_person, x_leads_deep). Usage is only implied by 'search' plus the syntax examples, which help query construction but not tool selection.

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