agentscan: download the full current snapshot

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

Goes well beyond the readOnly/idempotent annotations: gzipped delivery, per-source row cap, 1-5 s latency, USD 2 price with no free tier and a per-IP daily cap, plus a prompt-injection safety warning about treating endpoint/URL/on-chain strings as untrusted. These are exactly the operational traits an agent needs before calling.

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?

Front-loaded with the action and scope, then cost/timing/safety details, all of which earn their place. Minor redundancy: 'Returns every current-snapshot record' largely restates the opening sentence.

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 return shape need not be explained. The description covers scope, fallback tool, cost, rate cap, latency, and data-trust caveats, leaving nothing material missing for a zero-required-param read tool.

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 100% and there is only one optional parameter already documented as 'Filter: exact source id.' The description restates this ('optional `source` to restrict to one source') without adding format or matching semantics, so the baseline 3 applies.

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 and resource ('download the full current snapshot of the index') with explicit scope (all sources, per-source row cap, gzipped). It names the contrasting sibling export_agent_index, so an agent can distinguish them without opening a schema.

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?

Explicitly routes the agent: use this for the full snapshot, use export_agent_index for a filtered slice, and the `source` param restricts to one source. The when/when-else conditions are stated outright rather than left to inference.

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