coverage_report

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

No annotations provided, so description must fully explain behavior. It omits side effects (e.g., destructive?) and doesn't clarify 'acknowledge' meaning. Lacks safety or side-effect details.

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?

Three sentences, front-loaded with core purpose, no waste. Efficient and to the point.

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?

Describes return concept (ADDED/REMOVED) but lacks specifics on format, pagination, or examples. Adequate for a simple tool but missing details for full completeness.

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 already covers the single param 'env' with description. The tool description does not add further meaning beyond schema, so baseline 3 is appropriate.

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 clearly states it diffs live schema against baseline snapshot, explaining ADDED/REMOVED items. It uniquely identifies the tool's purpose among siblings.

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?

Mentions running 'npm run snapshot' to acknowledge, but doesn't explicitly compare to siblings like schema_check or state when not to use. Usage context is implied, not clear.

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