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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add substance — and it does, disclosing the returned fields (titles, summaries, place counts) despite there being no output schema. It omits ordering, pagination, and roughly how many guides exist, which are the remaining gaps.

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 front-loaded sentence with the resource, its 'Published' scope, and the URL pattern packed into a parenthetical that earns its place. Nothing is redundant.

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 parameters and no output schema, the description carries the return-value burden and does so by naming the fields returned. For a simple catalogue listing it is close to complete, though a note on result size or ordering would fully close it.

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?

The tool takes zero parameters, so the schema baseline applies and no parameter explanation is needed. The description wisely spends its words on scope and return content instead.

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 identifies the resource precisely: published Fulham-themed guides, with the URL pattern showing a {slug} identity. It is clearly distinct from get_guide (single guide) by being a listing, though it never states that distinction 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 by the resource being a collection; there is no explicit 'use this when you want the catalogue' statement and no mention of get_guide or search_places as alternatives. The 'Published' qualifier hints that unpublished guides are excluded, which is a small piece of scoping guidance.

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