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

The annotation readOnlyHint=true already establishes that this is a safe read operation, so the description need not restate that. The description adds useful context about the content structure (e.g., 'hash-chained audit events'), but does not disclose behavioral details such as filtering semantics, pagination, or result limits beyond what the schema suggests.

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 a single, tightly written sentence that front-loads the verb and resource, followed by a compact list of contained elements. Every word contributes value; there is no redundancy or filler.

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?

While the description lists the content of evidence packs, it omits essential operational context: how the parameters filter results, whether limit applies to packs or items, any pagination or ordering behavior, and the structure of the response. With no output schema, the description carries the burden of explaining return semantics and partially fails to do so.

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%; the description provides no explanation for the parameters limit, user_id, agent_id, or server_id. It does not state how these filters affect the returned evidence packs, nor does it add any semantic meaning beyond the schema's bare property names. This is a significant gap for a tool with four optional parameters.

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 uses the specific verb 'Return' and clearly identifies the resource as 'Verify Ledger evidence packs', listing the exact content types included (invocations, hash-chained audit events, decisions, outcomes, mandates, cost summaries). It is unambiguous and differentiates from sibling tools that target other report types.

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?

No explicit guidance is provided on when to use this tool versus alternatives. There is no mention of scenarios, exclusions, or related tools for different query types. The description only states what the tool returns, leaving the agent to infer usage context.

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