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

The annotations already establish readOnlyHint=true and openWorldHint=true, and the description adds materially useful behavior: pricing at $0.002 USDC per successful call, x402 payment on Base/Solana/Arc, and that failed calls are free. It stops short of covering auth requirements, rate limits, or error behavior beyond the billing note.

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?

Two sentences, both front-loaded with purpose and scope before the billing details. Every clause contributes either routing information or behavioral context, with no wasted phrasing.

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 simple one-parameter identity lookup with an output schema and annotations present, the description is complete: it says what is returned, what is excluded, where the data comes from, and how billing works.

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% and the sole parameter already has a description with examples, so the schema carries parameter semantics. The description only restates that the input is one ticker, adding no syntax or format detail beyond what is already structured.

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 states a specific resource and scope: company identity for one stock ticker, enumerating company name, legal name, ticker, and page description. It also explicitly excludes financial figures, which meaningfully distinguishes it from the many stock-price and market-data siblings.

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?

It gives clear context: use this for company identity from the public stock page, and not for financial figures. However, it does not name a specific alternative tool for price or financial data, so the routing guidance is strong but not fully explicit.

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