Fetch Financial Evidence

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

Annotations already establish read-only and idempotent behavior, and the description adds meaningful context: evidence is untrusted, responses are transport status only, and no evidence evaluation or Evidence Carrier verification occurs. This prevents an agent from overinterpreting what the tool returns.

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 tight sentences with the action front-loaded and the critical caveat immediately after. There is no filler, and it does not repeat what annotations or the schema already provide.

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 tool with three parameters, sibling tools, and no output schema, the description leaves too much unspecified: parameter semantics, return-value structure, and when to choose this tool over alternatives. The transport-only caveat is useful but not enough to make the definition complete.

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 description does not explain any parameter meaning. The word 'bounded' is a weak implicit hint about size limits, but it does nothing to clarify the required topics array or the timeout and max_bytes controls.

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 names a specific verb and resource: fetch JSON from fixed named routes, with useful qualifiers like bounded, untrusted, and read-only. It is clear what the tool does, but it does not explicitly contrast with the sibling tools financial_evidence_topics and financial_evidence_route, so it falls short of top-tier differentiation.

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 gives no guidance on when to use this tool versus its siblings, no explicit 'use X instead' conditions, and no exclusion criteria. The status-report caveat is behavioral information, not selection guidance.

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