get_ap_aging

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

No annotations are provided, so the description carries the full burden, and it does disclose the key trait — 'Read-only report' — which is the main safety signal an agent needs. It says nothing about scope filtering (org/period), rate limits, or data freshness, so the disclosure is partial rather than rich.

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?

A single compact sentence with the brackets enumerated inline and the safety trait appended at the end. Nothing is redundant and the resource is front-loaded.

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 zero-parameter report with no annotations and no output schema, the description covers purpose, output content (the five aging brackets), and safety. It stops short of specifying the reporting period or the granularity of the returned amounts, but it is otherwise sufficient to call 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?

The tool takes zero parameters, so there is no parameter semantics burden to carry; the baseline of 4 applies. The description's enumeration of brackets is about output content, not inputs.

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 ('Get') and resource ('accounts-payable aging brackets') and defines exactly what the report measures: how much is owed to vendors and how overdue. By framing the scope as amounts owed to vendors (payables), it implicitly separates itself from the sibling get_ar_aging, which covers receivables.

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?

The description implies the reporting use case (understanding vendor obligations by overdue bucket) but never states when to call this versus get_ar_aging, get_trial_balance, or the search_* tools. No prerequisites or exclusions are given, so usage must be inferred from the name.

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