current_tariff

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does not indicate whether the tool is read-only, requires authentication, or has any side effects. The agent cannot infer safety or cost implications from this description alone.

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 extremely concise at four words, but this brevity sacrifices informative detail. While it is front-loaded, it does not fully earn its place as it omits important context. A few more words to clarify the output or usage would improve it without sacrificing conciseness.

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 has no parameters and an output schema exists, the description is partially complete. However, it lacks usage guidelines and behavioral transparency. The agent could infer basic functionality from the name and siblings, but additional context would significantly improve completeness.

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?

There are zero parameters, and schema coverage is 100%. Per guidelines, the baseline for 0 parameters is 4. The description adds no parameter-specific meaning, which is acceptable since there are no inputs to describe.

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 'Currently active tariff per fuel' clearly indicates that the tool retrieves the currently active tariff and implies it is per fuel type. It distinguishes itself from siblings like 'compare_tariff' (comparison) and 'list_products' (listing products). However, it could be more explicit about the verb (e.g., 'get') and exactly what 'per fuel' entails.

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 provides no guidance on when to use this tool versus alternatives such as 'compare_tariff' or 'get_product'. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name and title.

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