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

Annotations already establish this is a safe, idempotent, closed-world read operation. The description does add genuinely useful domain caveats beyond annotations—award values are not payments and overlapping/federal sources stay labelled—which help prevent misinterpretation, but it says nothing about result size, year coverage, or pagination.

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?

Three compact sentences with no filler, and the core resource description is front-loaded. The domain caveat and the omission clause are both earned.

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 annotations covering safety and no output schema, the remaining gaps are modest: name handling is only implied and sibling differentiation is absent. For a single-optional-parameter read tool the caveats provided are largely sufficient.

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 schema has a single parameter at 0% description coverage, so the description must compensate. It does partially by explaining that omitting name lists bodies and implying name selects a specific body, but it never states the expected name format or matching behavior.

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?

It states a specific resource (a public body's reported values, by year and source, plus largest suppliers) and notes it matches the body's page. It does not, however, distinguish itself from overlapping siblings like get_totals, get_supplier, or get_department.

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?

Usage is only implied by the final clause 'Omit name to list bodies,' which describes two modes of one tool rather than when to choose this over alternatives. No alternatives are named and there are no exclusions, so an agent has weak routing guidance among 14 siblings.

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