get_execution_status_counts_by_assignee

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

No annotations are present, so the description must disclose behavior. It explains parameter formats (cycles comma-separated, project/version accept keys/names/ids, -1 for Unscheduled) and the return map structure. However, offset and limit parameters are not explained, and there is no mention of authentication, rate limits, or error cases.

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 concise with two main sentences and inline parameter notes. It avoids unnecessary verbosity while conveying key information. The structure is functional, though the inline notes could be slightly clearer in a separate section.

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?

Given the complexity (5 parameters, no output schema, no annotations), the description covers the main return format and parameter quirks, but lacks explanation for offset/limit, error handling, and prerequisites (e.g., project existence). It provides enough for basic usage but leaves gaps.

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 add meaning. It clarifies the cycles format and the flexible input types for project/version. However, offset and limit are left unexplained, and the default value for cycles (empty string) is not discussed.

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 the tool returns per-assignee status counts for given cycles, and specifies the output as a map with status fields. The name and phrasing distinguish it from the sibling 'get_execution_status_counts' but does not explicitly state the difference.

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 provides one concrete use case ('spot workload imbalance or bottlenecks'), but does not specify when to avoid using it or mention alternative tools like 'get_execution_status_counts' for aggregate counts.

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