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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful report semantics by explaining supplier grouping and the specific aging buckets, though it does not describe permissions, pagination, or return format beyond that structure.

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 two tight sentences with the report definition front-loaded ahead of usage guidance. Every sentence carries useful information and there is no filler.

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?

For a three-optional-parameter report tool with rich annotations and full schema coverage, the description is largely complete: it defines the report, its aging buckets, and when to use it. The main minor gap is that it does not explicitly distinguish this from get_bills or get_aged_debtors as alternatives.

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 company, as_of_date, and contact_id are already fully documented in the schema. The description does not add parameter-specific meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 report resource and scope: outstanding bills grouped by supplier and bucketed by days past due. It distinguishes itself from related siblings such as get_aged_debtors and get_bills through the creditor/owe-focused framing and explicit aging buckets.

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 concrete user phrases that should trigger the tool, such as "who do I owe", "what bills are due", and "show aged payables", plus the planning-supplier-payments scenario. It does not explicitly name when not to use it or point to alternatives such as get_bills or get_aged_debtors.

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