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

Annotations already cover read-only, open-world, and destructive hints. The description adds useful context by referencing a 'last fetched' state, implying the tool compares against a previous fetch. However, it does not disclose whether the tool performs a new network fetch, updates internal state, or how the diff is returned.

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 clear sentence with no filler and the core purpose is front-loaded. It is concise, though it could have included parameter or usage details without becoming bloated.

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?

With an output schema present, return values need not be described, and annotations cover safety traits. Still, the description omits essential context about what 'includeDiff' controls, whether a live fetch occurs, and how the last-fetched baseline is established. An agent would likely need to inspect the output schema and infer behavior.

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 description coverage is 0%, and the description does not explain either parameter. 'url' is only implicitly tied to 'a page,' and 'includeDiff' is left entirely to inference from its name. The description adds no explicit meaning beyond the bare parameter names.

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 states a specific action ('check whether a page has changed') and a clear resource ('a page since it was last fetched'). This uniquely distinguishes it from sibling tools like crawl, extract, and scrape, which perform fetching or extraction rather than change detection.

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?

No guidance is given about when to use this tool versus alternatives, nor any exclusions or prerequisites. The description only implies a use case (change detection) but does not explain when to prefer it over crawl, fetchMore, or scrape.

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