Url Diff

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

The description adds context beyond annotations: no JavaScript execution, no access control bypass, caching behavior with fresh parameter. Annotations already indicate non-read-only and non-destructive, and the description clarifies the caching side effect.

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 three sentences, front-loading the purpose, then usage constraints, then parameter guidance. No unnecessary words.

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 description covers purpose, parameter usage, and constraints. It assumes understanding of 'bounded normalized diff' and does not explain behavior when no previous snapshot exists, but output schema provides return value details.

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 detailed descriptions. The tool description largely paraphrases the schema—e.g., 'Pass url as an absolute public HTTP(S) URL' mirrors the schema's description. It adds no new semantic value beyond emphasis.

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 'Return a bounded normalized diff against the previous snapshot,' specifying the verb and resource. Among many URL tools, this one is uniquely about diffing, so it stands out.

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 provides explicit usage constraints: 'Use only for public HTTP(S) resources' and guidance on the fresh parameter. However, it does not explicitly compare to siblings like url_changed to help decide when to use this tool.

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