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 of behavioral disclosure. It effectively describes key behaviors: items start unchecked, can be ticked off in the app, and the tool returns a confirmation with title and item count. However, it doesn't cover potential errors, permissions, or rate limits, leaving some gaps for a mutation tool.

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 well-structured and front-loaded with the core purpose, followed by usage guidelines and return information. Every sentence adds value without redundancy, making it efficient and easy to parse for an AI agent.

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 a good job covering the tool's purpose, usage, and basic behavior. However, as a mutation tool, it could benefit from more details on error handling or side effects, though the return confirmation is adequately described.

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 documents all parameters. The description adds value by explaining the purpose of items ('Each string becomes one checkbox item, initially unchecked') and providing context for day parameter usage in common patterns, but doesn't elaborate on trip_key or title beyond what the schema states.

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 ('Adds') and resource ('a checklist to a Wanderlog trip'), making the purpose specific and unambiguous. It distinguishes this tool from siblings like wanderlog_add_expense or wanderlog_add_note by focusing on checklists, not other trip components.

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 this tool, including 'Add at least one checklist per trip' and common patterns for different contexts (e.g., 'On the trip (no day)', 'On day 1', 'On specific days'). It also distinguishes usage from siblings by specifying checklist-specific scenarios, though it doesn't explicitly name alternatives.

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