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

Goes well beyond the readOnly/idempotent annotations by disclosing output size (800-1500 words, longer than other tools), exact document structure, print/site-file formatting intent, and that the region drives which WHS/CDM/OSHA legislation is cited. The [PRO] marker signals the api_key gating requirement. Nothing here contradicts the readOnlyHint, since generation has no side effects.

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?

Front-loaded with the artifact definition, then use-case, then output structure, then examples — a logical order an agent can parse quickly. The three example tasks add length but each demonstrates a different trade/region pairing, so they earn their place; the section enumeration is slightly verbose but maps directly to the return value.

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?

There is no output schema, and the description fully compensates by describing the three output sections and expected length. Combined with 100% schema coverage on the 7 parameters, an agent has everything needed to decide to call it and to construct correct arguments.

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 real signal by giving three concrete example task strings that illustrate the expected granularity for the `task` parameter and the region/trade combination. It also implicitly reinforces that region must not be assumed, matching the schema's explicit warning.

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 artifact: 'Generates a complete Risk Assessment and Method Statement (RAMS) document', and even maps the artifact to regional names (JHA, SWMS). The enumerated output sections (Hazard Register, Method Statement, Qualifications) make it unmistakably distinct from siblings like generate_safety_checklist or check_compliance.

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 a clear trigger condition: 'Use this tool when a foreman or PM needs a formal safety document before a high-risk task.' The regional-jurisdiction note further narrows appropriate use. It stops short of naming when NOT to use it or pointing to the sibling checklist/compliance tools for lighter-weight needs.

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