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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the result is a preformatted markdown report intended to be rendered verbatim, and the aggregation is done server-side in one call. No auth/rate-limit detail, but little is needed for a zero-param read 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 sentences, front-loaded with the core value proposition ('in ONE call') and then the contents. The 'render verbatim' instruction is compactly placed at the end. Nothing is wasted.

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?

No output schema exists, but the description explicitly covers the return format (preformatted markdown report) and how to handle it (render verbatim). Combined with the enumerated contents and covered annotations, an agent has everything needed to call and use this 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?

The tool takes zero parameters, so the schema carries nothing to interpret and the baseline is 4. There is no parameter syntax or filtering behavior to explain, and the description correctly does not invent any.

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?

States a specific verb and resource ('Daily FSM operations brief in ONE call') and enumerates the exact contents: open jobs by status, scheduled-today/unassigned/unscheduled counts, per-technician load, oldest open jobs, overdue-AR total. This distinguishes it from partial siblings like todays_schedule, tech_workload, and ar_aging, which each cover only a slice.

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?

Gives explicit trigger phrases ('morning brief', 'ops report') that map user intent to the tool. However, it does not say when to prefer the granular siblings (todays_schedule, tech_workload) over this aggregate, nor any exclusions, so it stops short of full when/when-not guidance.

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