budget_burndown

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

Discloses that it reads budget config and archive, returns per-envelope data with unmapped spend, and implies no destructive behavior. Without annotations, this provides good transparency, though could explicitly state it is read-only.

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 sentences, front-loaded with purpose, each sentence adds value without waste. Efficient and clearly structured.

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?

Adequately explains output (target, actual, remaining, unmapped spend) and edge case. With an output schema present, full return details are not needed. Slightly lacks mention of permissions or limitations.

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 description specifies the 'month' parameter format as YYYY-MM, adding meaning beyond the schema's type string; with 0% schema description coverage, this is valuable context.

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 compares planned target vs. actual spend per envelope for a given month, and mentions it reads budget config and categorized archive, distinguishing it from siblings like budget_forecast or spending_summary.

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?

No explicit guidance on when to use this tool versus alternatives; does not mention when-not-to-use or provide selection criteria relative to siblings.

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