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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds nothing beyond that: no mention of the default page size of 30, the 100 cap, ordering, or whether cursor paging is expected to reach all results. For a list tool whose main behavioral risk is incomplete retrieval, that is a real gap.

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?

It is a single short sentence with no filler or redundancy, but the brevity comes from under-specification rather than discipline. There is no front-loaded statement of what the call does.

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 six optional parameters, a cursor-based pagination model, and no output schema, the description should explain what is returned and how paging works. It provides none of that, leaving the agent unable to predict the response shape or confirm that the field list is output rather than filter input.

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 67%, leaving limit, status (enum open/incomplete/complete) and the required/optional semantics undocumented. The description only echoes 'status' and 'project' and says nothing about search text matching, mine_only scoping, or cursor/limit interplay, so it does not compensate for the coverage gap and arguably muddies whether the listed fields are inputs or outputs.

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 is a noun fragment ('To-dos with project, priority, status, due date and assignees') that essentially restates the name and title. It never uses a verb like 'list' or 'retrieve', and it is ambiguous whether the enumerated fields are returned fields or available filters (status and project map to params, priority/due date/assignees do not). A reader must infer the operation from the tool name alone.

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 call this versus get_todo (single record) or the other list_* siblings, and no mention of pagination workflow despite a cursor parameter. The agent gets context only implicitly from the name.

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