get_team_workload

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

With no annotations, the description carries the behavioral burden. It discloses that the tool groups open and completed tasks by assignee and operates account-wide or by project. It does not mention read-only guarantees, response shape, or aggregation details, but for a simple read-style aggregation the provided behavior is reasonably clear.

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?

A single sentence that states the core action, grouping dimension, statuses included, and scope. There is no filler or redundant restating of the tool name.

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 one-optional-parameter read tool, the description covers the essential selection behavior and scope. Without an output schema, it does not describe the returned format, but the aggregation intent is clear enough for an agent to select and invoke the tool correctly.

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 coverage for the only parameter, project_id, is 100%, and the schema already explains it as limiting the view to one project. The description's phrase 'across the account or one project' reinforces the optionality, but it does not add meaning beyond the schema.

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 states a specific verb-resource pairing: 'Group open and completed tasks by assignee' and clearly scopes it 'across the account or one project.' It is clear but does not explicitly position itself against sibling tools like get_all_tasks or get_time_report, so it stops short of full differentiation.

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 when to use this tool: when an assignee-level overview of open and completed tasks is needed, optionally limited to one project. However, it gives no explicit guidance about when not to use it or how it compares to alternatives such as get_tasks_by_status, get_project_stats, or get_time_report.

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