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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description nonetheless adds two useful behavioral facts: the response is GeoJSON, and the zone must be open — a precondition that hints at a failure mode. It still says nothing about what happens if the zone is closed or about error shape.

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 short sentences with the return format and subject front-loaded. The trailing 'Stuart: GET /v2/areas/{zone}' reference is mildly redundant but cheap and occasionally useful for tracing.

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 read-only two-parameter lookup with full schema coverage and no output schema, stating the GeoJSON return type and the open-zone requirement covers what an agent needs. The only real gap is behavior on a closed or unknown zone.

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 100% with both parameters described, and one carries an enum, so the schema does the heavy lifting. The description only reinforces the zone-name convention and the picking/delivering split already present in the schema, adding no new syntax or format detail.

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 a specific resource (a zone's picking or delivering coverage area) and the exact return type (GeoJSON), with concrete zone examples. It is clearly distinguishable from the nearest sibling, stuart_get_zone_schedule_slots, though it never states that contrast explicitly.

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 phrase 'open Stuart zone' implies a precondition (the zone must be open) but does not spell out when to choose this over the schedule-slots or ETA tools. No explicit exclusions or alternatives are given.

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