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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add operational context, which it does: only published guides are returned, and the payload includes the introduction plus ranked places with sourced fields. It does not address missing-slug behavior or truncation.

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?

A single dense sentence, front-loaded with the resource and identifier before the return contents. 'Every field sourced' is slightly cryptic but earns its place by flagging provenance.

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 burden of describing the return value, and it does so (introduction, ranked places, sourced fields) for a two-parameter read tool. Minor gaps remain around error behavior for unknown or unpublished slugs.

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%, so the schema already explains that slug comes from list_guides and that limit caps places at 50 (default 25). The description only echoes the slug concept and adds nothing about the limit parameter, which is the correct baseline.

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+resource: fetch a single published Chelsea guide identified by slug, returning its introduction and ranked places. The singular 'one ... guide by slug' implicitly contrasts with the sibling list_guides, but no sibling is named 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?

Usage is only implied: the singular, slug-keyed lookup signals 'use this to read one guide, not to browse'. There is no explicit when-to-use or when-not guidance and no routing to list_guides, get_place, or compare_places.

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