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

Annotations already establish read-only, idempotent, non-destructive, and non-open-world behavior. The description adds useful operational context beyond annotations, including a 32 KB payload note, 60 RPM rate limit, demo/L402 access paths, and an HTTP 400 invalid-input behavior.

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 front-loaded and compact, with no wasted sentences. The final operational sentence is dense and slightly awkward, mixing payload size, rate limit, parameters, auth options, and error behavior into one clause.

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?

Given the output schema, full schema description coverage, and annotations, the description provides enough context for an agent to understand the task, when to select it, and key operational constraints. The main remaining issue is the curious 'defaults to standard' phrasing, but overall completeness is strong.

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 100%, including enum documentation for audit_focus, so the schema already carries most parameter meaning. The description adds little beyond mentioning original_context and compacted_summary, and the parenthetical saying compacted_summary defaults to 'standard' is confusing because the schema marks it as required with no default.

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 states a specific verb and resource: auditing a compacted summary against the original full context for dropped constraints, file paths, altered numbers, and pending tasks. It also distinguishes the tool from summarize_technical_document, so an agent can separate this verification task from summary generation.

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?

It explicitly says when to use it: verifying that an LLM context-compaction summary retained task-critical facts before truncating history. It also names the alternative summarize_technical_document for generating a new executive summary from a raw document.

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