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

The readOnlyHint annotation already signals a safe read operation. The description adds useful behavioral context by indicating that results are filtered to tasks whose specific attributes are accessible to the caller, which hints at permission-based scoping. It does not describe pagination, ordering, or return shape, but the annotation lowers the burden.

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 a single, tight sentence that leads with the action and resource, followed by the key scoping condition. There is no filler or repetition of schema or annotation information.

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 simple one-offset list operation with a readOnly annotation, the description is minimally viable. However, it leaves offset semantics and the output format to inference, and the access-filtering phrase is vague enough that an agent may not know exactly which tasks are returned. Extra detail about the return value or pagination behavior would improve completeness.

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 does not explain the offset parameter at all. While the parameter name suggests pagination, the tool description adds no meaning beyond the schema's type and default. The description should have compensated for the missing schema documentation but 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?

The description states a clear verb and resource ('List tasks') and adds a scoping condition (tasks whose rubric, funding, and visibility are accessible to the caller). This differentiates it from single-task reads like read_taskhol. However, the phrase 'fixed rubric, funding and visibility' is a somewhat opaque way of describing access filtering, so it is not quite a 5.

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?

No explicit guidance is given about when to use this tool versus alternatives such as read_task, search, or create_task. The listing behavior is implied but no exclusions or conditions are stated, leaving the agent to infer when list_tasks is preferred.

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