wanderlog-mcp

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

With no annotations provided, the description carries the full burden. It effectively discloses behavioral traits: it's a read-only operation (returns a URL), describes permission levels for each mode (full-permission, read-only, suggest-mode), and mentions sharing implications. However, it doesn't cover potential errors (e.g., invalid trip_key) or rate limits, leaving minor 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?

The description is front-loaded with the core purpose, followed by structured details about mode variants and a clear default rule. Every sentence earns its place: the first states the goal, the next explains mode options, and the last provides usage guidance. No wasted words, and it's appropriately sized for the tool's complexity.

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?

Given no annotations and no output schema, the description does well by covering purpose, usage, and parameter context. However, it doesn't specify the return format (e.g., a string URL) or error handling, which could be useful for an agent. For a simple URL-fetching tool, it's nearly complete but has minor omissions.

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 baseline is 3. The description adds value by explaining the practical meaning of mode variants beyond the schema's enum list: it clarifies that 'edit' is for owners, 'view' is safe to share, and 'suggest' allows collaborators to propose changes. This enhances understanding but doesn't fully detail trip_key semantics beyond referencing wanderlog_list_trips.

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 clearly states the verb ('Returns') and resource ('the wanderlog.com URL for a trip'), specifying it's for opening in a browser. It distinguishes from siblings like wanderlog_get_trip (which likely returns trip data) and wanderlog_list_trips (which lists trips), focusing specifically on URL generation rather than trip content manipulation.

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?

The description provides explicit guidance on when to use different modes: 'edit' for owners, 'view' for safe sharing, and 'suggest' for collaborative proposals. It also offers a decision rule: 'If you don't know which mode the user wants, default to edit.' This gives clear alternatives and a fallback strategy.

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