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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the ownership constraint, which is useful authorization context, but does not disclose not-found behavior, return shape, or other edge cases.

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?

The description is one short sentence with no wasted words, and the key scoping information ('one task', 'owned by the caller') is front-loaded. It does not repeat structured data from the schema or annotations.

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?

For a read operation with a single required parameter, full schema coverage, and annotations covering safety and idempotency, this description is sufficient for an agent to select and invoke the tool correctly. The ownership constraint is the only non-obvious contextual detail and it is present.

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%: the lone id parameter already has a type and description. The tool description does not add extra meaning about the parameter format or semantics, so the baseline of 3 is appropriate.

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 states a specific verb ('read'), a clear resource ('one task'), and a scope qualifier ('owned by the caller'), which distinguishes it from sibling tools like tasks_list (multiple tasks) and tasks_next. It is not a tautology because it adds the ownership constraint.

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 phrase 'one task' implies this tool is for fetching a single task by id, while tasks_list or tasks_next serve other retrieval cases. However, it never explicitly names alternatives or states when not to use this tool, so some routing is left to inference.

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