Read a Wanderlog travel guide

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the guide is public and that the tool renders full content as readable text, which establishes a safe read operation, but it does not mention error behavior for missing or private guides, authentication requirements, or rate limits.

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 description is two tight sentences that front-load what the tool does, then supply the parameter source and the sibling alternative. Every sentence earns its place, with no wasted wording.

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 read-only guide-fetching tool with no output schema, the description gives a clear high-level account of what is returned: sections, places, notes, and readable text. It does not explain failure modes for invalid or private guide keys, but the essential information needed to invoke the tool correctly is present.

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 all three parameters, including the day filter and response_format enum, are already documented in the schema. The description mentions passing guide_key from a search response, but that repeats the schema description rather than adding new semantics, so the baseline of 3 is appropriate.

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 gives a specific verb and resource: fetches the full content of a public Wanderlog guide, including sections, places, and notes, and renders it as readable text. It also clearly distinguishes this from wanderlog_get_trip for the user's own trips, so an agent can tell the tools apart without opening either schema.

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?

It explicitly states when to use it (reading a public Wanderlog guide, using a guide_key from a wanderlog_search_guides response) and when not to use it (for your own trips, use wanderlog_get_trip instead). This names a concrete alternative and the condition that selects it.

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