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

readOnlyHint=true already declares the safe-read profile, so the bar is lowered. The description usefully names the underlying endpoint (GET /api/tasks) and the exact field set returned, but says nothing about truncation/no-pagination or result limits, which the schema covers instead.

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 compact sentences, front-loaded with the verb and resource, with the endpoint appended last. The parenthetical field enumeration is dense but has no wasted prose.

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 compensates by listing the returned fields, and it covers the main filter modes plus my_tasks. An agent has enough to call it correctly, though it lacks guidance on interleaving typed filters with the raw `where` string.

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 description coverage is 100%, so every parameter (including where, include, limit) is already documented in the schema. The description only restates filters and glosses my_tasks in nearly the same words the schema uses, adding little beyond the structured fields.

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 and resource ("List tasks") and enumerates the returned fields plus the filter dimensions (project, task list, assignee, completion), so the agent immediately knows this is a filtered list, not a single-fetch. It does not explicitly contrast itself with paymo_get_task or the other list_* siblings, which keeps it off a 5.

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?

It names the filter axes and clarifies the my_tasks flag, which implies when to use it, but never says when to prefer paymo_get_task, paymo_list_tasklists, or how to combine filters with the raw `where` clause. Usage is inferable rather than stated.

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