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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description adds that results are grouped by section and what each checklist covers, which is useful but not deep behavioral disclosure (no pagination, caching, or auth notes).

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?

Two sentences, with the return behavior front-loaded and the usage cue trailing. The variant enumeration is long but each item earns its place by clarifying distinct outputs; nothing is wasted.

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 single-enum, read-only lookup with no output schema, the description covers what is returned and when to use it. Return-value structure is described at a high level (grouped by section), which is sufficient given there is no output schema.

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% with the lone param being an enum whose description is just 'Which checklist.' The description compensates by spelling out what each of the seven options actually contains (8-week countdown, moving day, first-night box, US/CA/UK change of address, 12-week international), which meaningfully aids selection beyond the raw enum values.

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 (Returns) and resource (one of Haulest's checklists), and enumerates the seven checklist variants so the agent knows exactly what content is available. It is clearly distinguishable from siblings like search_moving_guides or estimate_moving_cost.

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?

Gives one triggering condition ('Use it when someone wants a to-do list for a move') but names no alternatives or when-not conditions. Adequate context, but the agent gets no guidance on how this differs from search_moving_guides for the same intent.

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