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

With no annotations, description fully carries burden: details computation source, performance stats, signing, payment model, and failure mode. Excellent disclosure.

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 purpose, then details. Slightly verbose with performance stats, but all sentences add value. Could be trimmed slightly without loss.

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?

No output schema, but description explains return behavior with and without payment. Inferred successful return is a signed score. Adequate for a paid API 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% with descriptions for both parameters; description adds no significant new information beyond schema, only minor context (e.g., agent on public ledger).

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?

Clearly states it computes a validated Altman Z-score for a single equity ticker, with specific metrics. Distinct from sibling tools (claim_verdict, file_dispute, screen_entity, verify_receipt).

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?

Mentions paid nature and payment requirement, but does not explicitly contrast with siblings or provide alternative scenarios. However, the purpose is clear enough for an agent to decide when to use.

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