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

readOnlyHint=true already declares the safety profile, so that adds nothing. The description contributes no behavioral context beyond a REST path: nothing about default sort order, page-size default behavior, what the response contains, or whether filters combine with AND semantics — all of which matter for a paginated filtered list.

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 actual behavior, with no filler. The trailing API path is slightly redundant but tiny and potentially useful for correlating with API docs.

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 8 parameters, pagination, and filters but no output schema, the description should at least sketch what comes back (task summaries with cursor-based paging) or note that the filters are combinable. It does not, leaving the schema to carry the load — adequate but thin for an endpoint of this surface area.

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 75%, so several parameters (cursor, page_size, project_id, status_ids, assignee_ids, incomplete_only) are already documented in the schema. The description adds nothing to those, and sort_by/sort_order carry enum values but no explanatory text in either place. Baseline 3 for a mostly-covered schema.

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 with scope attached ('List the tasks of one project'), which cleanly separates it from gorelo_list_projects and from the ticket/client list tools. It stops short of explicitly differentiating itself from sibling list endpoints, but the resource is unambiguous.

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 when-to-use guidance, no mention of alternatives for cross-project task listing, and no note that project_id comes from gorelo_list_projects (that hint lives only in the schema). The REST endpoint reference ('GET /v1/projects/{projectId}/tasks') does not help an agent decide when to call it.

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