list_billing_products

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

Since no annotations are provided, the description carries full burden. It discloses client-side filter application, case-insensitive partial matching, and return of non-deprecated products. It does not detail the response structure, which is a minor gap.

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: purpose first, then filter behavior, then usage guidelines. No wasted words; every sentence adds value.

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?

Without an output schema, the description could better specify the response format (e.g., list of products with fields). However, it covers essential behavioral aspects and usage context, so it is nearly complete.

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?

With 100% schema coverage, baseline is 3. Description adds value by providing concrete examples for the filter parameter and clarifying that contract comes from get_billing_profile, going beyond schema basics.

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 explicitly states 'Search the IONOS CLOUD product/pricing catalog by keyword', clearly defining the verb (search) and resource (product/pricing catalog). It distinguishes itself from sibling tools that list other entities, and explains the client-side filtering behavior.

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?

Provides explicit guidance: 'Only call this tool when the user has explicitly specified a product or category... If the user asks a broad question... do NOT guess keywords... instead ask the user...' Also includes examples of valid filters.

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