Snapshot Diff

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

No annotations provided, but the description explains return format (additions, removals, changes) and first-call fallback. Could be improved by explicitly stating it's read-only or non-destructive.

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: core function, usage guidance, and edge case. No fluff, each 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?

For a simple diff tool, the description covers purpose, usage, edge case, and optional refinement. Differentiates from sibling 'snapshot' and no output schema needed as return is described.

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% with descriptions for both parameters. The description adds slight value by explaining the selector parameter's purpose, but sessionId is not elaborated beyond its name.

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 tool compares current page state against last snapshot, returning only changes. It distinguishes itself from sibling 'snapshot' by highlighting token savings.

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 advises using after 'act' instead of 'snapshot' when only changes needed, and mentions using 'selector' to scope. Also covers first-call behavior.

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