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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a definitional detail — that the count covers 'active' jobs and the forward window is 7 days — but discloses nothing about freshness, aggregation basis, or scope limits, which is thin for a reporting 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?

Two compact sentences, zero filler, with the returned content front-loaded before the usage hints. Every clause carries information an agent can act on.

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 parameterless aggregation with no output schema, the description tells the agent what it will get and roughly when to use it. What is missing is the granularity of 'active' and any alternative routing, but nothing essential to invoking it is absent.

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 zero parameters, so the baseline is 4; there is no parameter surface the description needs to compensate for, and the schema is trivially fully covered.

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 names a precise verb+resource: per-technician active job count plus jobs within a 7-day forward window. This is a distinct aggregation output that an agent can separate from siblings like technician_jobs or get_tech_performance, though it never names those siblings to sharpen the contrast.

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?

It supplies user-intent keywords ('who is busy', 'workload', 'capacity'), which implies when to reach for it, but gives no when-not conditions and does not point to any alternative tool for related questions (e.g. technician_jobs for detailed job lists, nearest_technicians for proximity).

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