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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond those: the response is a sample, no wallet or payment is required, and the paid tool costs 0.015 USDC. It does not mention rate limits or whether returned data is live versus illustrative.

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?

A single front-loaded sentence with the [FREE] tag first, then purpose, then payment/argument constraints. Every clause adds information and there is no filler.

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 zero-argument preview with rich annotations, the description states what it is, that it is free, and that no input is needed. It could briefly describe the sample content (multi-source social/trending topics) beyond the parenthetical, but it is adequate for calling the tool correctly.

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?

Zero parameters with 100% schema coverage, so the baseline is 4. The description confirms 'no arguments needed', which aligns with the empty input schema and avoids any confusion for the agent.

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 it is a sample response for social_trends_pulse and names the paid sibling immediately, with [FREE] front-loaded. An agent can distinguish it from the paid tool, though it doesn't differentiate itself from the many other *_preview siblings.

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?

Explicitly frames the use case: 'see the shape before paying 0.015 USDC' and notes no wallet, payment, or arguments are needed. It implies the paid social_trends_pulse as the alternative but doesn't state when to switch to it, keeping this short of a 5.

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