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 explains that notes 'appear inline between places in a day' and serve as 'connective tissue,' clarifying their role in itinerary construction. It also mentions the return value ('confirmation of where the note was added'), though it doesn't detail permission requirements or mutation effects beyond the implied creation action.

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 efficiently structured: the first sentence states the purpose, the second explains the functional role, and subsequent sections provide usage guidelines and examples without redundancy. Every sentence contributes directly to tool understanding, making it front-loaded and waste-free.

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 the tool's moderate complexity (3 parameters, no annotations, no output schema), the description is largely complete. It covers purpose, usage context, and behavioral role, though it lacks details on error conditions, authentication needs, or the exact format of the return confirmation, which would be beneficial for full agent guidance.

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%, providing baseline documentation for all parameters. The description adds minimal semantic value beyond the schema, only implying through examples that 'text' should be practical travel advice rather than arbitrary content, but doesn't elaborate on parameter interactions or constraints.

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 specific action ('Adds a text note to a Wanderlog trip') and resource ('Wanderlog trip'), distinguishing it from sibling tools like wanderlog_add_place or wanderlog_add_expense by focusing on textual annotations rather than physical locations or financial items.

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 ('after adding each place or group of places') and includes five concrete examples of appropriate note content (e.g., transportation tips, booking advice), giving clear context for application without needing to specify exclusions.

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