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

Annotations already establish readOnly/idempotent/non-destructive, yet the description adds real behavioral substance: the regulatory test applied (1.45-8(c)(2)), what the return contains (countable apprentice hours vs excess hours), the consequence for excess hours (stay in total labor hours, paid full journeyworker prevailing rate), and honest flagging that the hours-only path is an interpretation rather than a strict result.

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?

One dense paragraph, so the core rule and the controlling input are front-loaded, but heavy inline CFR citations and stacked parentheticals (1.45-7(b)(7)(iii), 29 CFR 5.5(a)(4)(i)) slow parsing. Every clause arguably earns its place, but readability suffers.

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 carries the return-value explanation itself (countable hours plus excess hours) and covers the hours-only edge case, which is the main complexity. The remaining gap is routing guidance relative to sibling compliance tools.

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 is 100%, so the baseline is 3, but the description adds meaning beyond it: journeyworker/apprentice headcounts are 'the controlling input', apprentice_hours_by_person lets the excess be measured per person, and the ratio parameters are defaults interpreted as the program ratio (1/1 or 2/1 examples).

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 concrete computation: given program ratio and daily headcounts/hours, return countable apprentice hours and excess hours. That is a specific verb+resource and an agent can tell it apart from generic siblings, though it never names check_apprentice_hours or other ratio-adjacent tools to sharpen the boundary.

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 implies the input situation ('give the program ratio and, for each day, the headcounts...') and describes a fallback mode ('with hours only and no headcounts it prorates'), but it never states explicitly when to pick this tool over check_apprentice_hours or check_applicability, nor any exclusions.

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