Audit Log

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing it as a safe read operation. The description adds the verification aspect of the hash chain, which hints at its internal behavior (e.g., integrity check), but does not detail failure modes or performance implications.

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 sentence that is front-loaded with the action and resource. Every word is necessary; there is no wasted text. It is perfectly concise for the tool's purpose.

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?

The tool has an output schema, so return value details are covered. The description addresses the core purpose and verification aspect. However, it lacks usage context (e.g., when to use this vs. other read tools) and does not mention what happens with invalid paths or broken hash chains, leaving minor gaps.

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?

The schema description coverage is only 50% (path has a description, maxEntries does not). The tool description does not add any information about the parameters beyond what the schema provides. It fails to compensate for the missing schema description of maxEntries.

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 the action ('Read') and the specific resource ('mutation audit log') with the additional purpose of verifying its tamper-evident hash chain. This distinguishes it from sibling tools like sdlc_read_file or sdlc_repo_snapshot, which serve different read purposes.

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?

The description implies the tool is for reading and verifying the audit log, but it does not explicitly state when to use it versus alternatives, what prerequisites are needed (e.g., permissions), or when not to use it. The context is clear but lacks exclusion guidance.

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