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

With no annotations provided, the description does a good job: discloses cost ($0.01/call), payment method (USDC on Base), no account/key needed, failure behavior (503, no charge), and that it's relayed live from an upstream source. It lacks mention of rate limits or idempotency, but overall transparent for a simple read tool.

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?

Three sentences, each carrying key information: what it does, how to use it, cost/behavior. No fluff, front-loaded with the core purpose. Every sentence earns its place.

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 no parameters, no output schema, and no annotations, the description covers all needed context: real-time nature, sentiment analysis, ranking, cost, failure mode, auth requirements (none), and output format. It fully equips an agent to understand and invoke 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?

No parameters in the schema, so coverage is 100%. The description adds value beyond the schema by explaining the output format (structured JSON with sentiment, ranked headlines) and the cost model, which is essential for an agent to decide to invoke it.

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 it provides 'real-time crypto market news with sentiment analysis and top headlines ranked by importance', specifying the verb (relay/get), resource (crypto news), and distinct features (sentiment, ranking). This distinguishes it from sibling tools like crypto_feed_since or scan_crypto_market.

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 states it's a one-request, no-parameter call for latest market-moving stories, suitable for trading agents and research pipelines. It also mentions failure mode (503, no charge). While it doesn't explicitly list when not to use or compare to alternatives, the zero-parameter nature and clear purpose make usage obvious.

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