tariff_calculator

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

Without annotations, the description carries the full burden. It states 'Estimate' implying a calculation, but provides no details on behavioral traits like data sources, accuracy, or that it's a demo version. The 'DEMO' tag suggests limited functionality but isn't explicit.

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 very concise, one sentence front-loading the purpose. The 'DEMO' could be made more informative while maintaining brevity, but overall it is efficient and not verbose.

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 the tool is a calculator with two parameters and an output schema, the description lacks details about return value format, units, or how the estimate is computed. It provides minimal context for correct invocation, especially considering the 'DEMO' nature.

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 description coverage is 0%, so the description should explain parameters. It does not mention 'monthly_units_kwh' or 'customer_type', leaving the agent to infer meaning solely from the schema. No added value 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 the tool estimates monthly KPLC electricity cost for a Kenya household, with a specific verb and resource. It distinguishes from sibling tools (energy rights, subsidies, connection guides, solar options). However, the 'DEMO' tag introduces some ambiguity about reliability.

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?

No guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, limitations, or situations where other tools might be more appropriate.

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