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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the bar is lower. The description adds useful context beyond them by disclosing the returned content: each todo's due timing, rationale, where it is performed, and completion status.

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, front-loaded with the release_id branching and zero filler. The parenthetical item enumerations are long but they earn their place by previewing the returned checklist contents.

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 carries the burden of describing returns, and it does so adequately by listing what each checklist item contains and the two list variants. Minor gaps remain (no mention of todo identifiers that would feed close_todo/set_todo_done), but it is complete enough to call correctly.

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, but the description adds meaning beyond the schema by explaining the concrete output consequence of omitting release_id (switching to the 'Set up once' list) rather than just restating the field.

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 (list) and resource (release checklist) and splits the behavior into two clearly named modes: the release's 'Around the release' checklist vs. the artist's 'Set up once' list. An agent can distinguish it from sibling list_todos/list_tracks 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?

Explicitly states the condition that selects each mode (pass release_id vs. omit it), which is real usage guidance. It stops short of naming alternatives or exclusions relative to siblings like list_todos or the mutation tools (close_todo, set_todo_done), so it is clear context rather than full routing.

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