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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description needn't restate it. It does add useful behavior context by disclosing that results are filtered to open and overdue tasks and carry assignee and due date, but it doesn't address team scoping or whether the caller's own tasks are included.

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?

A single sentence with the scope and returned fields front-loaded; every word carries information and there is no boilerplate or repetition.

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 no parameters and rich annotations, the definition is close to sufficient, and naming the returned fields partly compensates for the absent output schema. However, it leaves open whether 'the team' means all members or the caller, and says nothing about volume, ordering, or whether completed tasks ever appear.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond scope. The baseline for a zero-parameter tool applies, and the description's scoping statement is consistent with an empty 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?

The description names the specific resource (tasks) and narrows the scope to open and overdue items for the team, plus the fields returned (assignee, due date). That is enough to separate it from the write-oriented siblings createTask and updateTaskStatus, though it never says so 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?

There is no explicit 'use this when' statement and no alternative named among the many other fetch*Context tools. The scope restriction to open and overdue tasks implicitly signals when the tool is appropriate, which is the minimum viable level of guidance.

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