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

Adds substantial context beyond the read-only and open-world annotations: the 24-hour window, exclusion of giveaways/bots/paid promotion, unverified and potentially coordinated posts, and the warning not to treat it as a trading signal. It also discloses pricing and payment flow.

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 the core output and caveats, then clearly separates when to use, alternatives, parameters, and returns. Every section is purposeful, and the structure makes scanning easy.

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?

Despite no output schema, the description explains the return shape in detail and covers cost, quote behavior, limitations, alternatives, and parameters. An agent has everything needed to decide and invoke 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?

Schema coverage is already 100%, including examples and the either/or relationship between coin and query. The description restates the same parameter guidance and does not add meaningful syntax or edge-case semantics beyond the schema.

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 exactly what the tool returns: the mood on X about a coin or crypto topic in the last 24 hours, along with score, post volume, themes, and links. It clearly distinguishes itself from siblings by naming crypto_news for articles and crypto_market_pulse for metrics.

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?

Provides explicit when-to-use guidance ('You want to know what crypto traders on X are saying about a coin right now') and names alternative tools for different needs. It also explains payment behavior, including quote-before-pay and free failed calls.

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