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

Adds substantial context the annotations do not carry: per-batch pricing (0.075 USDC), parallel fetching, and atomic all-or-nothing failure semantics where a failed batch is not charged. It does not describe what a 'snapshot citation' actually produces or how long batches take, but the cost and failure contract is the key operational risk and it is disclosed.

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-loads the core identity, then cost and failure behavior, with no waste. The trailing 'MCP tool: `snapshot_citations`' restates the tool name and earns nothing, but it is a minor blemish.

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 paid, non-idempotent, open-world operation with no output schema, the description covers cost and atomicity well but leaves the agent dependent on the sibling tool to know what a snapshot contains. `include_content`, which materially changes the response and possibly the cost, is left entirely unexplained.

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 50%: the `urls` parameter is already documented in the schema, including the one-to-five constraint and the all-or-nothing note, so the description largely repeats it. The `include_content` boolean has no description in either place, so the description fails to 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+resource and scope: a batch version of `snapshot_citation` handling one to five URLs in a single, parallel-fetched call. The relationship to the single-URL sibling is stated outright, so an agent can pick between them without opening either 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?

Framing it as 'like `snapshot_citation` for one to five URLs in a single call' implicitly tells the agent to prefer the batch form when it has multiple URLs, and the all-or-nothing note signals when it is risky. There is no explicit 'use X instead when' statement for edge cases such as a single URL or when partial results are acceptable.

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