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

Beyond the read-only/idempotent annotations, the description discloses important behavioral traits: latest fiscal year may be incomplete, output is grouped by payee/agency/period, unnamed lines remain separate, individuals are never named, and legal interpretation caveats. These are substantive operational details an agent could not infer from annotations or schema alone.

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 dense and front-loads the core search behavior before filters and return semantics. It is appropriately sized for a complex dataset, though some legal caveats and the bi-weekly/annual warning are repeated in the schema and could be tightened.

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 burden of explaining return structure, and it does so: separate source lines grouped by payee, agency and report period, unnamed lines kept separate, plus payee status and Treasury report links. It also supplies the key caveats needed to use the results 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?

Schema description coverage is 100%, so the schema already documents all five parameters. The description reinforces that filtering is by named organisation payee, agency or agency group, and grouped minimum amount, but adds only modest meaning beyond what the parameter descriptions already state.

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 verb and resource: searching Treasury bi-weekly Judgment Fund payment lines in the MORVS Judgment Fund Register for one fiscal year. It clearly scopes the tool to payment-line records and distinguishes the bi-weekly product from the annual product, though it does not explicitly differentiate itself from the sibling judgment_fund_payee tool.

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 useful usage context: default fiscal year, warning that the latest published year may be incomplete, and that bi-weekly and annual products must never be added. However, it does not explicitly say when to use this tool versus the clearly related sibling judgment_fund_payee, leaving the alternative routing to inference.

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