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 description's added value is the "Team roles only" authorization restriction and the detailed breakdown of what the response contains. With no output schema present, spelling out the returned sections is genuinely useful. It doesn't state whether archived/completed tasks are included, a minor 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?

Two sentences, front-loaded with the report contents and closing with the use case and access restriction. The content enumeration is dense but each clause conveys a distinct returned section; no filler or repetition.

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 and no params, the description must carry the return-value burden, and it does so by listing every report section. Combined with the access note, an agent has enough to select and call it. Minor omission: no hint about scope limits (e.g., whether completed/archived projects or date ranges are included).

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?

The tool takes zero parameters, so the baseline is 4. There is nothing parameter-level for the description to disambiguate, and it correctly spends no words on inputs.

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 (a projects report) and enumerates the exact contents: per-project task counts by status, percent complete, dates, overdue counts, next milestone, plus workspace overdue/at-risk tasks and per-person counts. This clearly separates it from siblings like get_progress_trend, get_earned_value, or get_workload, which cover narrower analytics.

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 best single call for 'how are my projects doing?'" gives an explicit usage scenario and positions it as the aggregate alternative to multiple narrower calls. "Team roles only" adds a prerequisite constraint. It stops short of naming specific sibling tools it replaces or when not to use it, keeping it below a 5.

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