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

With no annotations provided, the description carries the full responsibility for behavioral disclosure. It explains the hash-matching semantics: a matching hash implies reuse of previous content, giving some insight into the tool's logic. However, it does not state whether the operation is read-only, what side effects (if any) occur, or what the actual return value looks like. For a tool with no annotations, this is a notable gap.

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 two sentences, concise and front-loaded with the primary purpose. The second sentence adds useful context about the hash parameter. There is no fluff or redundant information, though it could potentially be tightened further by integrating the usage instruction more efficiently.

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 tool with three parameters, one required, and no output schema, the description should clearly indicate what the agent receives as a result. It implies the tool will indicate freshness (via hash match) but does not specify the response format (e.g., boolean, hash, status). It also fails to mention any prerequisites or error conditions. While the core usage is clear, the lack of return-value detail makes it incomplete for agent planning.

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 67%, with known_hash and max_age_seconds already having descriptions. The description adds value for known_hash by explaining its purpose ('pass it as known_hash. A matching hash means the agent can reuse its previous content') but provides no additional meaning for the url parameter (which lacks a schema description) and doesn't mention max_age_seconds at all. Given the high schema coverage, the baseline is 3, and the added insight for known_hash does not elevate it further.

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 uses the specific verb 'check' and resource 'web page freshness', and states the exact purpose: determining whether a page should be read again. It also emphasizes the use case for agents with previously read content. This clearly differentiates it from the sibling tool freshgate_stats, which likely focuses on statistics rather than freshness checks.

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 explicitly states when to use the tool: 'Use this before re-fetching a URL that an agent has previously read.' It also gives context for passing the known_hash parameter. While it doesn't mention exclusions or name alternatives, the sibling freshgate_stats is clearly a different function, so no competing choice exists. This is adequate guidance without being exhaustive.

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