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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly spends its words on non-obvious behavior: the result is a point-in-time snapshot of a long-running job rather than a final answer, and the response carries a next_action directive. It stops short of describing polling etiquette beyond 'no loop' or whether repeated reads are cheap.

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, each load-bearing: what it does, what it returns in kind, and how to use it. The polling prohibition is prominent early rather than buried.

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?

There is no output schema, and the description compensates by naming the key response field (next_action) and the out-of-band completion signal (email). What remains unstated is the rest of the response shape and the idempotency cost of re-reading, but the calling agent has enough to invoke it correctly.

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?

Only one parameter (job_id) with 0% schema description coverage, so the schema supplies no semantics. The description implies job_id identifies a particular scrape but never states the format or where the id comes from (presumably mapsdata_start_scrape). Adequate but incomplete for the only input the agent must supply.

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 and resource ('Get the current state of one scrape') and bounds the scope to a single job, which separates it from the plural sibling mapsdata_list_scrapes. The added 'INSTANT SNAPSHOT of a job that runs for minutes to hours' tells the agent exactly what kind of object it is querying.

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 an explicit when-not ('Do NOT call it repeatedly in a loop') plus the correct alternative behavior instead of polling ('Read next_action in the response and follow it'). It also notes that email notification handles completion, so the agent knows polling is unnecessary — concrete routing guidance rather than implied usage.

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