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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description adds real value beyond them: unit conventions (ft, kt, s, F, mi), the 'directions FROM' convention, the conditional presence of now.scores ('when the worker has scored it'), and source/freshness metadata in the response.

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 tight sentences, front-loaded with the primary payload (record + current-hour scores) before the secondary conventions. The units line is dense but earns its place by removing ambiguity from the returned numbers.

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 does carry the return-shape burden and largely discharges it: it names the record, the now.scores structure, the go/caution/nogo vocabulary, and the metadata envelope. The gap is the input side — the keyed lookup semantics of spotId are left to the schema.

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 reported as 0%, so the description is expected to compensate, but it says nothing about the required spotId/path parameter. The only parameter guidance is the pattern and example inside the schema itself, not the description.

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 resource and scope: 'A single spot record plus now.scores (go/caution/nogo per activity for the current hour).' An agent can distinguish it from list_spots (plural) and get_activity_scores (activity-focused), though it never names those siblings explicitly to sharpen the contrast.

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?

There is no when-to-use statement, no prerequisites, and no alternatives named. The agent must infer that this is the single-record fetch keyed by spotId, and gets no guidance on when to prefer it over get_conditions, get_poi, or get_activity_scores.

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