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

With no annotations, the description carries the full burden of behavioral disclosure. It conveys the core computation (aging buckets and chase action tiers), but it does not explicitly clarify that this is a read-only planning tool rather than an execution tool that sends chase actions. No output format or side-effect details are provided.

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 a single, well-structured sentence with no filler. The core idea (invoice aging buckets) is front-loaded, and the action tiers add useful context without bloat.

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 simple two-parameter analysis tool, the description adequately explains the intent and inputs. However, with no output schema and no annotations, it should also clarify what the tool returns, such as bucket labels and action recommendations, which are only vaguely referenced by 'aging buckets' and 'chase action'.

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 coverage is 50% because only 'today' is described. The description adds the useful notion of lateness-driven bucketing, but it does not explain how the invoice fields (amount, due, paid, client) factor into the calculation or how 'today' anchors the aging. It partially compensates for the schema gap without fully resolving it.

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 clearly states the tool's function: grouping invoices into aging buckets and assigning a chase action based on lateness. It is distinct from siblings like cash_runway and subscription_audit because it centers on invoice-level receivables follow-up, though it doesn't name those alternatives.

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 context is implied rather than explicit: use it when invoices need to be bucketed by age and matched to a follow-up action. It does not state when to prefer this over sibling tools or mention any exclusions, leaving some inference to the agent.

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