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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond that: it flags the payload as 'untrusted', notes that responses are 'bounded', and explicitly disclaims evaluation and Evidence Carrier verification — important caveats an agent needs in order to trust the result correctly.

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 tight sentences, front-loaded with the core action and scope, followed by the critical caveat. Dense but every clause carries meaning; no padding.

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?

No output schema exists, but the description covers the response posture (transport status only) reasonably well, and annotations carry the safety profile. The main incompleteness is the undocumented parameters and the lack of any routing guidance relative to its two siblings.

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 none of the three parameters (topics, timeout, max_bytes) are mentioned in the description. 'Bounded' gives only the vaguest nod to max_bytes/timeout, and the topic enum values are nowhere explained, so the description does not compensate for the schema's silence.

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 ('Fetch') and resource ('bounded untrusted read-only JSON') with a clear scope limited to fixed routes. It does not, however, differentiate itself from the sibling tools financial_evidence_route or financial_evidence_topics, so an agent can't tell from this text alone why it should pick this vs. those.

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?

There is no explicit when-to-use guidance and no mention of the sibling tools. The only usage-adjacent content is a negative scope note ('evidence is not evaluated... verification is not performed'), which tells the agent what the result is not, but not when to call it.

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