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 mentions that expenses appear in the budget tracker and can be linked to places, and states the return confirmation. However, it lacks details on permissions, error handling, or side effects like how linked expenses affect the trip view, leaving some behavioral aspects unclear.

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 with three sentences: the first states the purpose, the second provides usage context and examples, and the third describes the return. Each sentence adds value without redundancy, making it appropriately concise and front-loaded.

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 complexity of a 7-parameter tool with no annotations and no output schema, the description does well by explaining the tool's purpose, usage context, and return confirmation. However, it could be more complete by detailing behavioral aspects like error cases or how the tool integrates with other trip features, slightly reducing completeness.

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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema, such as implying the purpose of linking expenses to places, but does not provide additional syntax or format details. This meets the baseline for high schema coverage.

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 budget expense') and resource ('to a Wanderlog trip'), distinguishing it from siblings like adding places, hotels, or notes. It explains that expenses appear in the budget tracker and can be linked to itinerary places, providing precise scope.

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 clear context on when to use this tool ('Use this after adding places to give the trip a cost dimension') and gives examples of expense types. However, it does not explicitly state when not to use it or name alternatives among sibling tools, such as when to use other budget-related tools if they exist.

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