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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so the safety profile is covered. The description adds genuine behavioral context by explaining the two response modes (overview vs. single checklist's items). It does not describe output shape, ordering, or how 'stage' affects results.

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 tight sentences with the resource named first and the parameter behavior front-loaded. The compact 'stance/pillars' phrasing is slightly cryptic but no sentence 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 two-parameter, read-only, output-schema-less tool, the description covers the main mode switch but leaves the return structure vague ('items') and the stage filter unexplained. An agent can call it correctly by omitting or supplying slug, but cannot predict what it will get back in much detail.

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 the baseline is 3. The description adds real meaning for 'slug' (it selects one checklist and returns its items) but says nothing about 'stage' beyond the schema's bare 'Ownership stage filter', leaving the filter's accepted values and effect unexplained.

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 names the resource (boating safety stance/pillars and checklists) and the concrete checklist types (pre-departure, winterize), and its second sentence explains the mode switch. It is clear enough to distinguish from siblings like get_state_boating_rules or search_guides, though the pairing of 'stance/pillars' with 'checklists' under one tool is a bit muddled.

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?

Usage is only implied through the 'Pass slug for one checklist's items' sentence: omit slug for the overview, supply slug for a specific checklist. There is no explicit when-to-use versus siblings, no mention of what the 'stage' filter is for, and no guidance on when this beats get_state_boating_rules.

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