Rename a day heading in a Wanderlog trip

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

No annotations are provided, so the description carries full burden. It clearly states the effect (renames heading), explains what headings are (itinerary titles), and documents the reset behavior. It does not mention side effects beyond renaming, but for a simple rename tool this is sufficient.

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 concise with three short sentences, each earning its place: first states the action, second provides context, third handles edge case. It is front-loaded and has no unnecessary words.

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 simplicity (rename a day heading) and the absence of an output schema, the description fully covers behavior, parameter details, edge cases, and context (headings appear in itinerary). No gaps remain.

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 coverage is 100%, but the description adds value beyond the schema: it clarifies that 'day' accepts multiple formats (e.g., 'day 3', 'May 4') and that 'heading' can be empty to reset. This enhances understanding of parameter usage beyond the schema's property descriptions.

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 explicitly states the tool renames day headings in a Wanderlog trip, using a specific verb and resource. It distinguishes itself from sibling tools (e.g., wanderlog_edit_note, wanderlog_remove_place) by being the only one focused on renaming day headings.

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 explains when to use the tool (replace headings with more descriptive titles) and includes a special case (empty string resets to auto-generated heading). While it does not explicitly mention when not to use it, the sibling tools cover different operations, making the intended usage clear.

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