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

While annotations indicate destructive and non-idempotent behavior, the description says 'retrieve', implying a read-only operation, which is partially clarified by mentioning cost. However, it lacks explicit disclosure of side effects beyond cost.

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 two sentences, front-loaded with the core purpose, and every word contributes meaning without redundancy.

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 single-parameter tool, the description covers its operation, output, and cost. It could be improved by noting error handling or issuer not found scenarios, but overall it is sufficient.

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 covers the single parameter fully, and the description adds value by detailing the output fields, giving the agent a clear expectation of what the tool returns.

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 retrieves a research profile on US municipal securities issuers and lists specific data points (issuer type, credit standing, etc.), distinguishing it from siblings that focus on addresses, companies, or other domains.

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 provides context by specifying the scope (US municipal issuers) and cost (Premium API, $0.25 USDC), but does not explicitly state when not to use or mention alternatives.

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