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

Beyond the readOnlyHint, the description discloses payment requirements (paid-only, $0.001 USDC per call), the payment flow (omit x_payment for challenge), freshness reporting, and the behavior of missing source links. It also states the tool preserves the free allowance, adding valuable context not in annotations.

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?

The description is concise and front-loaded with the core function, followed by payment details and a disclaimer. It is slightly redundant in repeating 'paid-only' and the cost, but overall well-structured and not overly verbose.

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 tool with no output schema, the description sufficiently outlines the return content (headlines, links, times, sentiment brief, analysis window, freshness). It also covers payment flow and disclaimers, making it complete enough for an agent to call correctly, though output format specifics are left unspecified.

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?

The input schema already fully describes the x_payment parameter with instructions on omission and retry. The tool description adds no additional parameter meaning, so it relies on the high schema coverage (100%). Baseline 3 is appropriate.

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 the tool reads importance-ranked crypto headlines with source links, publication times, and a sentiment-scored market brief. It distinguishes itself from siblings by focusing on current crypto news rather than recaps or other market data, and the 'not a recommendation' disclaimer clarifies its non-advisory role.

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?

The description implies usage when current crypto news is needed but does not explicitly contrast with alternatives like otto_news_recaps or otto_pm_crypto. It does provide practical constraints (paid-only, hourly snapshot) but lacks explicit when-to-use vs. when-not-to-use guidance.

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