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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely new context: no auth required ('Public access'), filtering is applied before pagination, and result priority is governed by demand and blockers.

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 purpose and followed by filtering/priority behavior; little waste. The middle sentence is dense and packs two distinct ideas, but nothing is padded.

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?

With no output schema, the description should carry return-value and parameter burden; instead it only loosely sketches the returned structure. The key 'view' switch that changes output shape and the cursor mechanics are undocumented, leaving real gaps for a 3-parameter tool.

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 0%, so the description must carry all parameter meaning and it largely does not. It explains only that supported_path_kinds is an optional pre-pagination filter; the 'view' enum (grouped vs paths) behavior and the cursor pagination contract are left entirely unexplained.

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 concrete verb+resource: finding actionable evidence gaps grouped by service, with the associated path tasks and their requirements. The domain jargon ('path tasks', 'contribution requirements') is opaque, but the core purpose is legible. It does not differentiate itself from close siblings like get_participation_inbox or get_agent_brief.

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?

No when-to-use/when-not guidance and no alternatives named among the ~50 siblings. 'Public access' describes auth, not applicability, and 'demand and blockers determine priority' only hints at ordering. An agent must infer all selection logic.

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