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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, but the description adds substantive behavior beyond them: 1-hour result caching with <5ms hits, $0.01 per call with the first 5 free, failed calls never charged, and the crucial disclosure that over-quota returns a payment-required quote rather than a fatal error, plus the retry path via agent_id/tx_hash.

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-loaded with the purpose and cleanly segmented by labeled sections, but it repeats the pricing model three times ($0.01 per call, first 5 free, then the top-up flow) and the trailing 'Example: get_hackernews_tech_pulse(query='example')' adds nothing. Dense but not wasteful enough to drop below a 4.

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?

With an output schema present, return values need not be described; the description still covers everything an agent needs to call correctly — auth modes, trial limits, cache behavior, failure semantics, and the payment recovery path. Nothing material is missing for a paid, idempotent read tool.

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 100%, so the schema already documents query, agent_id, and tx_hash in detail — the description's parameter guidance largely overlaps. It does add a coherent interaction rule (pass query as a non-empty string; omit agent_id/tx_hash during the 5 free calls, supply them for paid execution), which frames the conditional logic slightly better than the per-field descriptions alone.

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 and resource — 'Queries live HackerNews discussions, front-page velocity, and developer sentiment' — and scopes it to 'any framework, startup, or AI model'. An agent can immediately distinguish it from the sibling get_agent_wallet_status, which the description itself names as the quota-check tool.

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?

Explicit WHEN TO USE / WHEN NOT TO USE sections, with the alternative named ('use get_agent_wallet_status to check your remaining free trial quota or prepaid balance') and an exclusion for unrelated domains or binary media. Routing is fully determined without inference.

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