diff

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

Without annotations, the description explains the output (list of changed offsets with old/new values) and the step-by-step process. However, it does not mention whether the tool is read-only, or how missing labels are handled, leaving some behavioral gaps.

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?

Description is concise with no wasted words. Key information is front-loaded: purpose, then workflow, then parameter documentation. Every sentence adds value.

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 exists and parameters are simple, the description covers purpose, parameters, and usage pattern. It does not mention prerequisites (e.g., snapshots must exist) but is otherwise complete.

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?

With 0% schema description coverage, the description adds meaningful examples and purpose for both parameters ('label_a: First snapshot label (e.g., "before")'), which compensates well. Could include more format details but adequate.

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?

Description clearly states 'Compare two snapshots and report differences.' and identifies it as the core discovery tool for detecting byte changes after user actions, distinguishing it from siblings like list_snapshots or snapshot.

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?

Explicitly describes the workflow: take snapshot A, perform action, take snapshot B, then diff. Provides clear usage context though does not explicitly mention when not to use or list alternative tools, which are unnecessary given its unique function.

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