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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description usefully adds that results are item-level and include done status, but the phrase 'Items can be ticked off one by one' introduces ambiguity about whether this tool mutates anything, and nothing is said about ordering, pagination, or volume.

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 short sentences, front-loaded with the resource and scope; nothing is bloated. The second sentence about ticking off is vague and border-line filler for a read tool.

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-parameter read tool with full annotation coverage this is mostly adequate, but with no output schema the description should say what an item looks like (id, title, done flag) rather than the loose phrase 'with what is done'. The ambiguity around ticking items is left unresolved.

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 only one required string parameter exists, fully documented in the schema as an id or domain. The description only alludes to the programme implicitly and adds no format examples or fallback behavior, so it does not exceed the schema baseline.

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 precisely (the programme's to-do lists, item by item, with completion state) so an agent can tell it apart from sibling listers like list_next_steps or get_program_guide. It lacks an explicit verb, but 'lists ... item by item, with what is done' conveys a read of task items for a programme.

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?

There is no guidance on when to choose this over get_my_todo, list_next_steps, or list_my_programs, and no prerequisite or exclusions stated. The agent must infer usage from the name alone.

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