calculate_india_electricity_bill

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It explains progressive slab tariffs, presets, custom slabs, fixed charges, fuel surcharge, electricity duty, and mentions importable constants. However, it lacks details on error handling or rate limits.

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 three sentences and efficiently conveys the tool's purpose, presets, examples, and importable constants. It is front-loaded with the primary purpose and well-structured, though slightly dense.

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?

Given no annotations and no output schema, the description covers usage, presets, custom slabs, and examples. It references importable constants for custom use. The return format (calculated bill) is not explicitly detailed but can be inferred for a calculation tool.

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?

Input schema coverage is 100% with each parameter having a description. The description adds value by explaining the slab format (last can be 'inf'), mentioning importable constants, and providing example queries that demonstrate parameter usage. This goes beyond the schema alone.

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 purpose: calculating Indian electricity bills using progressive slab tariffs. It mentions specific presets (BESCOM, MSEB, BSES) and custom slabs, distinguishing it from sibling tools which handle different calculations (BMI, compound interest, etc.).

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?

Usage guidelines are provided via example queries ('electricity bill for 250 units in Bangalore (BESCOM)', 'Delhi BSES bill for 400 units with ₹100 fixed charge'), indicating typical use cases. While it doesn't explicitly state when not to use, the sibling list implies this is the only Indian electricity bill tool, making context clear.

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