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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), it discloses distinct behavioral traits: the first-call full-content dump, the checkpoint-must-be-persisted-after-processing discipline, no push subscription, no historical revision log, and the fact that the hosted endpoint reflects each deployment. These are exactly the operational traits annotations cannot express.

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?

Purpose is front-loaded, and every subsequent sentence adds a distinct operational fact (first-call behavior, checkpoint discipline, endpoint freshness, cadence, absence of push/history). No filler or repetition.

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 one-parameter polling tool with no output schema, the description covers purpose, sequencing, cadence and key limitations; annotations cover the safety profile. It is only slightly short of complete because it does not characterize the shape of the returned updates or any auth requirements.

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?

With a single parameter and 0% schema description coverage, the description carries the burden, and it does explain the role of 'known': the checkpoint passed back next call and the fact that empty input means a full dump. It does not explain the url/sha256 pair structure or the 1000-item cap, so it is strong but not complete.

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?

States a specific verb (poll) and resource (published site content), and the qualifier 'new or changed documents' plus the document types make clear this is an incremental-change feed rather than a single-document read like read_content or a query like search_content. An agent can distinguish it from all siblings without opening any schema.

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?

Gives concrete sequencing guidance: first call with no known entries returns everything, then persist the checkpoint only after processing every update and pass it as known next time, with a 15-minute polling cadence. It does not name alternatives (e.g., read_content for a single already-known document) or state when to avoid this tool, so it stops short of a 5.

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