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

Annotations already declare read-only, idempotent, and non-destructive hints. The description adds valuable behavioral context beyond annotations by disclosing the payment mechanism ('Paid via x402 or API key credits') and rate limits ('Free tier: 10 policy gate calls/day per client'). This helps the agent anticipate costs and usage constraints.

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 consists of two concise, front-loaded sentences. The first sentence states the core function and return values; the second adds pricing and rate limit context. No wasted words or repetition of schema details.

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?

With no output schema, the description correctly specifies the high-level return values (allow, deny, allow-with-limits). It also includes billing and quota context. However, it does not describe the return object's structure (e.g., whether reasons or metadata are included), which would be helpful for an agent for full understanding, but the current coverage is adequate for basic invocation.

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 schema provides 100% coverage with descriptions for all parameters. The tool description does not add parameter-specific semantics beyond what the schema already contains, so it meets the baseline for good schema coverage without exceeding 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 uses a specific verb ('Apply') and resource ('treasury policy') and clearly states the outcome ('return allow, deny, or allow-with-limits'). This distinguishes it from sibling tools like 'risk_score' or 'simulate' by defining a distinct decision output.

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 intended use case is implied ('Apply treasury policy to a proposed action'), but the description does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or when-not-to-use guidance. Sibling tool names offer context but aren't referenced.

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