get_crew_workload

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states the core resource and grouping but does not explain how date_from/date_to affect the results, whether all crews are included, or what the summary return structure looks like. This is minimal disclosure for a retrieval tool.

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 that is concise, front-loaded with the action and resource, and contains no redundant or filler content. Every word contributes to defining the tool's purpose.

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 annotations and no output schema, the description is the only guide for the agent. It lacks parameter meaning, usage comparisons to sibling tools, and return-value detail. For a tool that accepts optional date filters, this is incomplete guidance.

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 input schema has two parameters with no descriptions and 0% schema coverage, so the description must compensate by explaining them. The description does not mention date_from or date_to at all, providing no additional meaning about their format, optionality, or filtering behavior. Thus the description adds no value beyond the bare parameter names.

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 ('Get') and resource ('summary of open work orders grouped by crew'), making the tool's function clear. It also includes the intended purpose ('assess workload distribution and backlog per team'), which helps distinguish it from sibling tools like get_open_backlog that do not mention crew grouping.

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 a use case ('to assess workload distribution and backlog per team') but does not explicitly specify when to prefer this over alternatives such as get_open_backlog or get_overdue_work_orders. It offers no exclusions or when-not-to-use guidance, leaving the agent to infer the appropriate context.

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