finance_verify

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds what the verification covers (hashes, seven accounting identities, replay), but says nothing about what a failure looks like, whether verification is exhaustive or short-circuits, or how long it may take.

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?

A single compact sentence with the core action and scope front-loaded and no filler. It is efficient, though arguably under-specified rather than ruthlessly concise.

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 verification tool the interpretation of results matters most, yet with no output schema and no annotation or description coverage of return values, an agent cannot tell what a passing or failing verification looks like. The undocumented run_id compounds the gap.

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 description coverage is 0% and the lone required run_id parameter is undocumented in both schema and description. The description never mentions run_id, its format, or where an agent should obtain one, so the description does not compensate for the coverage gap.

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?

States a specific verb ("Verify") and enumerates the verified resources: artifact hashes, seven accounting identities, deterministic replay. This is far more concrete than a tautology. It does not, however, distinguish itself from the sibling finance_validate, which an agent will reasonably read as an alternative way to check the same output.

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?

No when-to-use guidance, no prerequisites, and no mention of when to prefer finance_validate or finance_doctor instead. With a near-identically named sibling, the absence of routing guidance is a real selection hazard.

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