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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description adds value beyond that: it states an API key is required and that the call costs no credits, plus that repeated reads are the intended update mechanism — practical operational context not present in the annotations.

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?

Three short sentences with the outcome front-loaded ('See where a collection has got to') followed by the concrete payload and then the operational notes. Slight wordiness in 'how much of the area is searched, how many places have arrived, and what it has cost so far', but every clause carries information.

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 no output schema, the description must convey what comes back, and it does list the three returned signals (coverage, arrivals, cost). Combined with the API-key and credit-cost notes, an agent has enough to call it correctly; only the distinction from get_coverage remains unaddressed.

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 100% and the schema already explains that the id is 'the collection's id, as create_collection returned it'. The description adds nothing about the id parameter, so the baseline of 3 applies — the schema does all the work here.

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 names the specific resource (a collection) and the three facts it returns — search progress, places arrived, and cost so far — which is more concrete than the title 'Read a collection' alone. It does not, however, distinguish itself from the sibling get_coverage or list_collections, so an agent must infer the boundary. Clear verb+resource with no sibling differentiation.

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?

'Read it again whenever you want an update' gives a real usage pattern (polling this tool for state changes), which is better than nothing. But it names no alternative and no exclusion — notably it never mentions create_webhook, which exists as a push-based sibling. Usage is implied rather than contrasted.

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