billy_update_bill

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

No annotations provided, so description carries full burden. It discloses the confirm safety mechanism and write nature, but omits other behaviors like return value, idempotency, or field update constraints. Adequate but not comprehensive.

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?

Extremely concise with only two sentences, front-loading the key verb and the critical usage constraint. No redundant information.

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 having 3 parameters including a nested object and no output schema, the description lacks detail on expected input format, output behavior, error handling, and prerequisites. The confirm pattern is described but other critical aspects are missing.

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 low (33%), and the description only adds meaning for the confirm parameter (required for execution with dry-run preview). For id and patch, no additional insight is provided beyond the schema, leaving the agent to guess valid fields.

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?

Description clearly states 'Update an existing bill', which is a specific verb+resource. It distinguishes from siblings like create or delete by name, but lacks detail on whether it's a partial or full update.

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 states 'WRITE — requires confirm:true', providing clear usage context. It implies a dry-run mode without confirm, guiding when to use it, though it does not explicitly contrast with sibling tools.

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