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

With no annotations, the description carries the full behavioral burden. It hints at deletion handling via 'deletion state,' but does not say whether deleted tasks are included by default, how results are ordered or paginated (only a 'limit' param exists), or whether any permission is required. For an 11-parameter read tool this leaves key behavior undisclosed.

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 front-loaded sentence that packs the full filter surface into one line with no filler. It is efficient, though the trailing enumeration is somewhat run-on.

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 list tool with rich 100% schema coverage and no output schema, the parameters are adequately covered. However, default deletion behavior, result ordering, pagination semantics, and the absence of any note on how it relates to search_tasks leave meaningful gaps for an agent choosing between siblings.

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%, so the schema already documents every parameter including aliases and date bounds. The description merely re-lists the filter categories and adds no syntax, default, or semantics beyond what the schema provides, which is the expected baseline.

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 (inspect/list) and resource (task backlog) and enumerates the filter dimensions it supports. It is clear what the tool does, but it never distinguishes itself from the closely related siblings search_tasks, my_work, and list_task_activity, which also return task collections.

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?

'Use this to inspect task backlog' frames a use case but supplies no when-to-use vs when-not guidance and never names an alternative such as search_tasks for keyword/full-text queries or my_work for the caller's own tasks. Usage is implied rather than stated.

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