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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the ability to filter by deletion state, but it does not explain default deletion behavior, pagination, ordering, or what the result looks like beyond what the schema already says.

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 front-loaded sentence that immediately says how to use the tool and then lists the relevant filter dimensions. It contains no filler and is appropriately sized for an overview.

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 an 11-parameter read-only list tool with complete schema coverage and clear annotations, the description is broadly complete: it identifies the tool's purpose and the filter set. Minor gaps around default deletion handling and pagination behavior are mitigated by the detailed schema.

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 parameter schema already documents all 11 parameters precisely, including aliases, date formats, and filter behavior. The description only lists filter categories at a high level and adds no syntax or semantics beyond the 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 states a specific verb (inspect) and resource (task backlog) and enumerates the filter dimensions, so the tool's basic function is clear. It does not explicitly differentiate this tool from the close sibling search_tasks or explain whether it is board-scoped versus cross-board.

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?

It gives clear usage context with 'Use this to inspect task backlog by...' followed by the available filters. It does not state when to prefer search_tasks, get_task, or my_work instead, but it provides enough context to know the intended use.

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