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

Beyond the readOnly/idempotent annotations, it discloses the full return contract (itemId stability, isChecked vs checkedByMe semantics on shared trips, flat task list with no subtasks, section-heading grouping order) and a usage constraint ('Never show IDs to users'). That is substantial behavioral context the annotations do not carry.

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 scoping constraint are front-loaded, and every sentence carries information (return fields, alternatives, ID-hiding rule). It is long but dense; the enumeration of return fields could be trimmed slightly without loss.

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?

With no output schema, the description compensates by fully describing the return shape and per-field semantics, plus the sibling routing needed for subsequent edits. An agent has everything required to call and interpret this tool.

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%, so both trip_id and checklist_id are already documented in the schema. The description's note that checklist_id reads a single checklist restates the schema's own text rather than adding new syntax or format detail, so 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?

The description opens with a specific verb and resource: 'Read every checklist on a trip with its items.' It clearly separates this read operation from sibling mutation tools (checklist_items_add, checklist_item_update, segment_delete), so an agent can distinguish it without inspecting other schemas.

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?

It explicitly states the trigger ('Call this before editing items so you have the item IDs'), offers a filtered variant ('Pass checklist_id ... to read just one checklist'), and routes each alternative operation to its dedicated sibling tool. This is near-complete when/when-not guidance.

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