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

The annotations already declare readOnlyHint=true, and the description's 'Read' is consistent with that. The description does not add much behavioral detail beyond the annotation, such as pagination or error behavior, but it also does not contradict the annotation.

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?

One short, information-dense sentence. It front-loads the action and resource, then specifies the returned content without any filler.

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 simple, read-only tool with one fully documented parameter and no output schema, the description is complete enough: it states what is returned and confirms the non-mutating nature consistent with annotations.

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% and the single parameter, 'plan', is already well described in the schema with an example link and id format. The tool description does not need to add more and does not provide extra parameter nuance.

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 uses a specific verb ('Read') with a clear resource ('the plan's shared checklist') and tells the agent what it will see ('open and done items, with item_id'). This clearly differentiates it from mutation-focused siblings like add_checklist_item and check_item.

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 read-only framing and the content specification make it clear this is the retrieval tool for the checklist. It does not explicitly mention when not to use it or name alternatives, but the sibling set and verb provide unambiguous context.

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