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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely non-obvious behavioral context: the presence of a relay block reporting whether the Chief relay is online, and user_options listing remediation steps when it is not. With no output schema, this partial disclosure of return shape is valuable, though it does not describe ordering, pagination, or volume of results.

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 aggregate scope before the trigger and the relay caveat. Every sentence carries information, though the relay/user_options sentence is slightly tangential to the core purpose and could be trimmed.

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 read tool with no output schema, the description covers what is returned (the three waiting categories plus relay block and user_options) and when to invoke it. It is adequately complete, missing only result ordering or size expectations.

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% and the single `project` parameter is fully self-documenting, including the "id or exact name" format. The description never references the parameter, so it adds no meaning beyond the schema; baseline 3 applies.

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-plus-resource scope ("everything waiting on the user across their Chief projects") and enumerates exactly the three categories it aggregates: open manager tasks, proposed milestones awaiting approval, and stalled work. This clearly distinguishes it from the narrower siblings list_manager_tasks, list_milestones, and get_project_status, which each cover only one slice.

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?

"Call this when the user asks what needs them" gives an explicit trigger condition, and the cross-project scope implicitly distinguishes it from the single-resource list tools. It stops short of naming an alternative tool or a when-not-to-use case, so it is clear 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.