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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world) with no contradiction. The description adds value beyond them: it discloses the return payload (ranked stops, detour minutes, nearby drives, planning link) and, unusually, licensing/attribution constraints for bulk extraction. No auth or rate-limit detail, but the addition is substantive.

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 lead sentence is promotional coverage statistics ('50 published drives today; strongest in the West and Southwest') that do not help an agent select or call the tool, and it occupies the front-loaded position. The genuinely useful content — return shape, slug source, license — is pushed behind it.

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 carries the return-value burden and does so adequately (ranked stops, detour minutes, related drives, continue-planning link). A single required param is fully documented in the schema. The main gap is sibling differentiation, which belongs to purpose/usage rather than completeness.

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 one parameter and 100% schema coverage, baseline is 3. The description goes beyond the schema by stating the slug must originate from list_drives, which is provenance information the schema's 'Published /drives slug.' does not convey.

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 operative sentence is 'Find stops along a published road-trip route,' which names a plausible action but not the one implied by the title ('Get one published Roamward drive') — the framing blurs into the sibling search_stops. It never states which single drive is being retrieved or how it differs from list_drives or search_stops. Purpose is inferable, not crisp.

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?

'Use a slug returned by list_drives' gives an explicit prerequisite and names the upstream sibling, which is genuine when-to-use guidance. It also states usage terms (individual-assistant use with attribution; license required for bulk/commercial use). It stops short of exclusions versus search_stops or plan_drive.

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