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

Annotations already cover readOnly/openWorld/non-destructive, and the description adds genuinely new behavior: the exact response shape { count, next_skip, items }, the pagination contract, and the single-record read path. It does not mention default page size (only the schema does) or error behavior, keeping it short of a 5.

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?

Extremely dense and front-loaded: fields first, then return shape, then paging, then filter strategy. The telegraphic 'Tasks: title, status (...)' opener is slightly cryptic but wastes no words.

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 10 optional parameters, a nested filters object, and no output schema, the description does the important work: it explains the return shape, paging loop, and the two filtering mechanisms. Minor gaps remain around sort/limit and taskGroupId, but an agent can call this correctly from the description plus schema.

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; the description earns extra credit by enumerating the filterable field names (title, dueDate, assignedTo, projectId, taskBoardId) and the status enum values, which helps an agent construct filters. It omits sort, limit, and taskGroupId semantics that the schema carries.

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 (Tasks), the filterable fields, and the endpoint (GET /tasks), so there is no ambiguity about what is returned. It implicitly separates itself from plutio_list_task_boards / plutio_list_task_groups by scoping to tasks, but never states that distinction explicitly.

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 gives concrete usage modes: 'Pass id to read one record' versus 'Filter with exact-match fields or a MongoDB-style query', plus the paging loop (pass next_skip as skip). It does not say when to prefer this over siblings such as plutio_create_task or plutio_update_task, but for a read tool the operational guidance is clear.

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