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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description adds real behavioral context: items are created 'all unchecked', the call 'runs without asking' because it affects no one outside the trip, the checklist is deletable in the app, and it requires a Cotlet API key with app access. This meaningfully informs the agent about auth needs and reversibility.

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?

Purpose and resource are front-loaded, and the three sentences each carry distinct value (what it creates, how it behaves, what auth it needs). Minor mild redundancy between the purpose and the creation sentence, but overall tight.

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?

For a create tool with no output schema, the description covers purpose, scope, day-vs-trip behavior, auth requirements, and reversibility. Well documented by the schema's parameter descriptions. Little an agent needs to call it correctly is missing.

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 four parameters (including the day-omission behavior and the trip_id source). The description's 'items you pass, all unchecked' merely echoes the schema's own wording, adding no new parameter meaning. Baseline 3 applies.

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?

States a specific verb and resource ('Creates a checklist') and adds distinguishing scope: packing, to-dos or shopping lists, for the whole trip or a single day. An agent can tell this apart from wanderlog_add_note, wanderlog_add_expense, and wanderlog_add_place without opening any schema.

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 use cases (packing, to-dos, shopping) and scope (whole trip vs one day) imply when to reach for this tool, but it never explicitly contrasts with sibling organizers like add_note or add_place, nor states a when-not condition. Usage is implied rather than spelled out.

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