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

Annotations already mark this as read-only, open-world, and idempotent, and the description adds meaningful behavioral detail beyond them: data is verbatim from FWC, stamped with version/published-year, CC BY 4.0, unknown awards throw, and the result is not legal advice. This is rich context for an agent deciding to call the 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?

The description is four sentences, front-loads the core purpose, and every sentence earns its place: what is returned, how to filter, provenance/versioning, scope limits, and error behavior. There is no filler or repetition of the title or annotations.

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?

Given there is no output schema, the description fully compensates by describing the return content (base and calculated rates with operative dates), filtering options, data source, licensing, caveats, and the unknown-award error. An agent has enough information to decide when and how to call this 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?

Schema description coverage is 100%, so the baseline is 3. The tool description lightly echoes 'award code or fixed id' and 'filtered by classification level or employee-rate-type', but it adds no parameter-level detail beyond what the schema already provides; therefore it does not deserve a higher score.

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 specific operation and resource: returning 'Minimum pay rates for an Australian modern award' from the Fair Work Commission MAPD. It clearly distinguishes the tool from siblings like award_allowances and award_penalties by emphasizing 'Dollar values only' and pay-rate scope.

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 gives clear context on how to invoke the tool (award code or fixed id, optional filters) and explicit exclusions: it does not say which award applies or what is payable, and should be read with the award. It does not name alternative sibling tools directly, so it stops just short of fully explicit routing guidance.

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