Fetch Financial Evidence

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

Annotations already declare readOnly/openWorld/idempotent and non-destructive, but the description adds genuinely useful context beyond them: the payload is 'untrusted', response size is 'bounded', status reports transport only, and evidence is neither evaluated nor verified. That tells an agent not to trust or over-interpret the content.

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 dense sentences with no filler, and the core action is front-loaded before the caveats. Minor jargon load, but every clause carries information.

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 undocumented parameters, no output schema, and specialized vocabulary, the description leaves too much unsaid. It never explains what a topic selection or timeout does, nor what the fetched JSON structure looks like, so an agent lacks what it needs to invoke it precisely.

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 coverage is 0% with 3 parameters, so the description carries the full burden, yet it mentions none of them. The word 'bounded' loosely gestures at max_bytes but gives no meaning for topics (the required enum array) or timeout.

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) and names the fixed routes it draws from. However, the route names (LiquiLens, Undertow, Seiche, Palimpsest) are opaque and it never distinguishes itself from siblings financial_evidence_route or financial_evidence_topics.

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 when-to-use guidance and never names an alternative tool or the condition that selects one. Its second sentence covers behavioral caveats (what is not evaluated) rather than routing guidance.

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