Get Group Delivery Overview

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds that it uses aggregation and sampling, indicating not all data is returned, which is useful beyond annotations.

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?

The description is a single sentence, front-loaded with the verb 'Aggregate', but given 7 parameters, it is too concise and lacks structure like bullet points or parameter breakdown.

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?

No output schema exists, yet the description does not explain the return format or structure of the aggregated overview. It only mentions using a single GraphQL query, leaving the agent guessing about the output.

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 description mentions 'sampled projects, open merge requests, open issues' corresponding to project_limit, merge_request_limit, issue_limit, but ignores assignee_limit, output_format, and project_nested_limit. With 0% schema coverage, the description should cover more parameters.

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?

The description clearly states it aggregates a group-level delivery overview with sampled projects, open MRs, and open issues via a single GraphQL query. However, it does not differentiate from sibling tools like portfolio_delivery_overview or team_delivery_digest.

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 implies usage when a quick group overview with sampling is needed, but provides no explicit guidance on when to use it vs. alternatives or what prerequisites exist.

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