check_url_updates

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

Description explains the detection mechanism (comparing Last-Modified headers) but does not detail what happens after detection (e.g., whether it triggers rescraping automatically, status reporting, or side effects like updating internal state). With no annotations, the burden is higher; partial transparency.

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?

Two sentences packed with essential information: purpose, method, and detection capability. No redundant words; well-structured for quick parsing.

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?

No output schema and no mention of return value (e.g., what data is returned, whether it's a list of updated documents or a boolean). Missing details on behavior when auto_rescrape is enabled, leaving gaps for the agent.

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 covers 100% of parameters with a clear description of 'auto_rescrape'. The tool description adds no additional meaning beyond what the schema already provides, so baseline 3 is appropriate.

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?

Clearly states it checks all URL-sourced documents for updates using Last-Modified headers. The verb 'check' and resource 'URL-sourced documents' are specific and distinguish from sibling tools like 'check_updates' (likely different resource) and 'scrape_url' (action).

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 on when to use this tool versus alternatives such as 'check_updates' or 'rescrape_document'. Does not specify prerequisites or when not to use it. Implied usage from purpose but lacks explicit context.

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