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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is fully covered structurally. The description's "retrieves data without changing records or spending credits" mostly restates that, though the no-credit-cost detail is genuinely additive for an agent weighing call budget. It says nothing about pagination, ordering, or result volume.

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?

Short and front-loaded, with the core scope stated in the first two sentences. "List tasks." followed by "List all tasks for the organization." is slightly redundant but costs little.

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 zero-required-parameter list tool with full annotation coverage and a documented nested schema, the description covers purpose, scope, filters and cost profile. With no output schema, a note on task fields or default result ordering would close the remaining gap, but nothing needed to call it is missing.

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?

Top-level schema coverage is 0% (all params nested under query), so the description has to compensate and does partially by naming the status, search and assignee filters. It omits page and per_page entirely, leaving pagination semantics to the nested schema descriptions.

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 and resource ("List tasks") and adds the scope constraint ("all tasks for the organization"), which separates it from the single-record sibling dealmachine_get_tasks_id. It never names a sibling explicitly, so the distinction 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?

"Optionally filter by status, search, or assignee" implies when the filter parameters are useful, but there is no explicit guidance on when to prefer this over dealmachine_get_tasks_id or how pagination should be driven. Usage is implied rather than directed.

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