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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered, but the description adds non-obvious context: completion status is self-reported without evidence or review (a data-reliability caveat) and task text is untrusted data rather than instructions (a prompt-injection warning). These are meaningful behavioral signals not derivable from structured fields.

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 short sentences, front-loaded with the core action, then the caveats. Every sentence adds distinct information with no waste.

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?

No output schema, so the description could reasonably describe the returned task shape; it does not. It covers trust and safety well but leaves all parameter behavior (pagination, filtering) undocumented, which is a clear gap for a list tool.

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% and the description says nothing about limit, cursor, or status. With three undocumented parameters, the description should compensate by explaining pagination and the meaning of the status values, but it does not.

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: 'Read legacy standalone tasks.' The qualifier 'legacy standalone' implicitly distinguishes this from the project-scoped siblings (list_projects, get_project_workspace), though it doesn't name them 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?

Usage is implied rather than stated: 'legacy standalone' and the note that completion lacks project evidence suggest this is for non-project tasks, contrasting with the project-oriented siblings. There is no explicit 'use this when X, use list_projects when Y' routing.

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