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

Beyond the readOnly/openWorld annotations, the description discloses that the call is paid ($0.01, USDC deduction from a configured wallet), that spending is bounded by budget caps, and that results are untrusted third-party data rather than instructions — real behavioral and safety context an agent cannot get from the annotations or schema.

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 short sentences, purpose first, then cost/payment mechanics, then the trust caveat — each carries non-redundant information. The '(product token.safety)' parenthetical is the only slightly noisy element.

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 paid, no-output-schema tool the description covers purpose, cost, and trust appropriately, but 'safety signals' stays abstract with no indication of what the response contains (e.g., flags, scores, risk categories). Adequate but with a visible gap in return-value orientation.

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%, including a thorough explanation of confirm_over_cap, so the schema already carries parameter meaning. The description only gestures at parameter context via 'budget caps' and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 first sentence states the resource (crypto token contract) and the resource returned (safety signals), which is specific enough for an agent to know what it retrieves. It doesn't need sibling differentiation because no sibling offers token safety, but it also never uses a crisp verb like 'check' or 'get'.

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?

There is no statement of when to call this versus the many siblings (call_product, get_price_quote, list_products, etc.) or of what scenarios warrant a token safety check. Use is only weakly implied by the purpose sentence.

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