issue_bill

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly warns that 'the bill cannot be edited or deleted' after calling, which is critical for an irreversible action. It also notes the financial consequence ('considered paid') and describes the return message format, adding valuable context beyond a simple operation.

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 concise and well-structured: a single sentence states the purpose and consequence, followed by clearly formatted Args and Returns sections. Every sentence earns its place with no redundancy.

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 tool with only two simple parameters and no output schema, the description is fairly complete. It covers the tool's behavior, the irreversibility, parameter meanings, and return value. It could be more explicit about prerequisites (e.g., bill must be in draft status), but overall it provides enough context for an agent to use it correctly.

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 input schema has no descriptions (0% coverage), so the description compensates with an Args section. It explains invoice_no as 'Invoice Number of the bill' and pay_method as 'Payment Method in uppercase letters' with examples (Cash, Card, UPI). This adds meaningful guidance, though it could be more exhaustive about valid values.

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 action: 'Issues a draft bill i.e. The bill is finalised and considered paid.' This provides a specific verb and resource, and distinguishes it from siblings like create_draft_bill and discard_bill by clarifying the finalizing and payment status.

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 description clearly implies when to use the tool: when you have a draft bill that needs to be finalized and marked as paid. It does not explicitly name alternatives or exclusions, but the context is clear given the sibling tools and the description's own wording.

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