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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuine value beyond them by enumerating the return payload (Sal's story, place and stretch, length, Wikipedia/source credit) even though no output schema exists, and it stays consistent with openWorldHint by limiting scope to Washington highways. It is silent on what happens when no story matches (empty result vs. error) and on any fuzziness in matching.

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 sentences, no filler: the trigger condition comes first, then the return contents, then the exclusions. Every clause carries information an agent needs, and nothing is repeated from the schema or annotations.

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 single-parameter read tool with rich annotations and no output schema, the description is nearly complete: it gives the trigger, the domain limit, and the return fields. The only notable omission is resolution behavior when a query matches nothing or matches multiple places, which would matter for a name-based lookup.

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 single parameter already documents that it accepts an id, title, or place name with examples, so the schema does the heavy lifting. The description restates the same three lookup modes without adding syntax, matching behavior, or format constraints, which is the baseline case for full schema coverage.

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 states a concrete verb+resource (retrieve Sal's story for a place/landmark/town along Washington highways, or by id) and lists what comes back (story text, place and stretch, length, source credit). It bounds the domain to Washington, which separates it from generic lookup tools, but it never names the closest siblings (stories_near, stretch_stories), so the boundary there is left to inference.

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 explicit when-to-use guidance ('Use this when someone asks for a story about a place, landmark, or town... or asks what Sal knows about a specific location or story by id') plus explicit when-not guidance ('Not for navigation, bookings, or places outside Washington'). The gap is that the exclusions target unrelated task categories rather than the real alternatives in the sibling set, so an agent comparing this to stories_near or stretch_stories gets no routing advice.

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