hyperd.budget.guardian

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

Discloses aggregation behavior, configurable window, return fields, exclusion of bridged USDC.e, and cost ($0.01 USDC) – all beyond what the input schema provides.

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 concise sentences, each adding unique value: function, usage guidance, and exclusions/cost. No wasted words.

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?

Despite no output schema, the description fully explains return data (total spend, breakdown, projected rate, under_cap flags) and cost. Covers all important aspects for an agent.

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 100%, so baseline is 3. The description adds context for cap_usd, explaining what response fields are included when it's provided, which adds meaning beyond the schema.

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 it aggregates USDC transfers for agent spend visibility, with a specific use case for budget enforcement before x402 calls. It distinguishes from sibling tools like balance.get or wallet.pnl.

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?

Explicitly says 'Use this BEFORE initiating the next paid x402 call' and notes what it does not count (bridged USDC.e). However, no explicit alternatives or when-not-to-use are given.

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