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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds return semantics ("returns who should act and an exact work-item revision") and the bounded-work-queue nature. It omits pagination/ordering behavior, which is the remaining gap.

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?

Three sentences, front-loaded with the core action and closed with the scoping negation; very little waste. The first sentence is slightly garbled ('blockers before open deadlines') but structurally efficient.

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 read-only, annotation-covered tool with no output schema, the description gives an adequate sketch of results (who should act, work-item revision). However it leaves pagination for limit/offset unexplained and never clarifies ordering or freshness, so it is adequate rather than complete.

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 33% — only projectId is documented (and well: 'project/mapping ID ... never a local path'). The description says nothing about the limit/offset pagination parameters, so it does not compensate for the coverage gap even though their intent is largely inferable from defaults and min/max bounds.

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 action and resource: reading "current dossier blockers before open deadlines and assigned work," i.e. a computed work queue. It also distinguishes itself from approval/notification siblings via the "not an approval, notification scheduler" clause, though it does not explicitly contrast with the closest sibling helvabase_work_items.

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?

The description frames when to reach for it (finding current blockers/deadlines/assigned work) and supplies explicit exclusions — it is not for approvals, notification scheduling, or RFP-coverage assertions. It stops short of naming the alternative tool to use for those cases, so it is strong but not fully routing.

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