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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a note about configurable MCP approval requirements and always-applicable business workflow approvals, which is genuine context an agent wouldn't otherwise have. It says nothing about pagination behavior or result shape, but the output schema carries that.

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?

Three sentences, none long, but the first sentence is generic product framing and the third is compliance boilerplate that only indirectly helps selection. The one operationally useful phrase is buried in the middle rather than front-loaded.

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?

Return values are covered by the output schema and safety by annotations, but an agent still cannot tell how this differs from `list_tasks`, what the ambiguous `id` parameter filters on, or how to page through results. For a list tool with four undocumented parameters, that leaves meaningful gaps.

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 0% across four parameters, so the description must compensate and largely does not. Only projectId is hinted at by 'tasks on a general project'; the `id` parameter (task ID filter? something else?) and the limit/offset pagination controls with defaults of 50 and a max of 100 go entirely unexplained.

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 sentence 'Read tasks on a general project' gives a verb and resource, so the basic purpose is inferable. But the description never distinguishes it from the sibling `list_tasks` (or `list_task_children` / `list_project_task_templates`), and the first sentence is generic product boilerplate rather than a statement of what this tool does.

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?

The only usage cue is the boilerplate 'Use this when working with RetailHardHat projects records in the connected organization,' which does not select between this tool and the many other list_* siblings. No when-not guidance and no named alternative for the obvious ambiguity with `list_tasks`.

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