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

Annotations already establish that the tool is read-only, idempotent, open-world, and non-destructive. The description adds useful context beyond annotations by explaining what evidence is preserved and by clarifying that prepared_response indicates availability, not freshness or readiness, while also stating account-access, advice, and execution boundaries.

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 front-loaded with the core purpose and is reasonably compact for the behavioral context it provides. The preserved-fields list is dense but earns its place by clarifying evidence handling.

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?

An output schema exists, so the description does not need to enumerate return values in full. It supplies the key caveat about prepared_response and the evidence-preservation behavior, though it remains incomplete on sibling differentiation and usage routing.

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?

There is only one optional parameter, and the schema already provides the title, default, pattern, and maxLength for it. The description echoes 'three-letter currency, default USD' and contextualizes it as funding evidence, but adds little parameter-specific meaning beyond the structured schema.

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 verb and resource: reviewing funding evidence and retrieving the bounded money-market table for one currency. It is clear what the tool does, but it does not explicitly distinguish itself from similarly named siblings such as financial_evidence_funding_review or financial_evidence_review.

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 implies usage through 'Review funding evidence for one three-letter currency,' but gives no explicit guidance on when to use this workflow versus the many sibling tools. It also provides no when-not-to-use routing or alternative selection criteria.

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