search_tariffs

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

No annotations are provided, so the description carries the behavioral burden. 'Discover' implies a read-only search and 'optionally narrowed' describes filtering behavior, but it does not disclose prerequisites such as whether the operator should be resolved first, what happens when no results match, or whether the output is limited to codes rather than prices.

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 a single front-loaded sentence with no filler. It states the core action first and then the optional modifiers, with every phrase contributing to the agent's understanding of what to pass and why.

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 low-complexity search tool with an output schema, the description covers the main operation and filter semantics. But there are no annotations, no guidance on sibling-tool workflows, and no statement about whether customer_type is required or what the default behavior is when optional filters are omitted.

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 must compensate. It maps customer_type to a 'customer profile' and clarifies that zone_preference and operator are optional narrowing filters. However, it does not explain what 'operator' means or the semantics behind the zone enum values, so the compensation is only partial.

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 uses a specific verb ('Discover') and a specific resource ('valid tariff codes'), and clearly scopes the results to a customer profile with optional zone/operator filters. This semantically distinguishes it from sibling tools like get_prices and get_tariff_components, which target different outputs.

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 implies when to use the tool: when tariff codes are needed for a customer type, optionally narrowed by zone or operator. However, it provides no explicit when-not-to-use guidance, no mention of alternatives, and does not explain how this tool relates to resolve_operator or get_prices.

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