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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the shape of the result set (one row per member with an overload flag), but says nothing about how capacity is derived, whether all-time or current-period data is returned, or how large workspaces are handled.

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 tight sentences with no padding. The output content comes first and the interpretive hint ('spotting over-assigned people') is deferred to the end, which is the right ordering.

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, the description usefully enumerates the returned fields, which is the key thing an agent needs. The remaining gap is temporal scope — it is unstated whether the summary reflects all current assignments or a period — but nothing else material is missing for a zero-argument read tool.

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 no parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline for a zero-parameter tool applies; no credit is lost, but the description also has no chance to clarify a scope argument (e.g. a date range) that would have been useful.

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?

Specific verb-plus-resource: returns a resource-allocation summary per workspace member, and names the three concrete outputs (allocated days, effective daily capacity, overloaded flag). It is clear what the tool produces, though it never distinguishes itself from the similarly-scoped get_workload sibling.

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?

'Useful for spotting over-assigned people' implies a use case but gives no when-to-use rule, no exclusions, and no routing to alternatives such as get_workload — an agent must infer which of the two workload views to pick.

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