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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), yet the description adds real behavioral value: it discloses the ordering rule ('Open tasks come first') and the identity of returned fields (who asked, what they asked for, which call, status). With no output schema, that field disclosure is genuinely useful; it stops short of stating limits or pagination.

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?

Two short sentences with zero padding: the scope and returned content come first, followed by the ordering rule. Every clause carries information an agent would otherwise have to guess.

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 read-only list tool with one optional boolean and no output schema, the description covers scope, ordering, and returned fields adequately. It lacks any note on result size or truncation behavior, which is a minor residual gap.

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 coverage is 100% and the single 'all' parameter is fully documented in the schema, so the baseline is 3. The description's 'Open tasks come first' indirectly signals the default behavior of excluding finished/declined items, but it does not explicitly tie that to the 'all' flag.

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 gives a specific verb and resource ('Lists the tasks') plus a precise scope ('handed to the signed-in person from their calls'), which separates it from a generic task listing. It does not explicitly name the single-task sibling (get_task) or get_action_items, so differentiation is inferred rather than stated.

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 by the scoping phrase (tasks assigned to the signed-in user, derived from calls), but there is no explicit when-to-use guidance, no statement of when to prefer get_task or get_action_items, and no prerequisites mentioned. An agent can infer the intent but is not routed.

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