Search subscriptions across products

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

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful context beyond those annotations: it returns status, expiry, and auto-renewal settings across all products, and clarifies that product-specific tools return the full record. It doesn't need to restate safety traits the annotations already cover.

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?

Two sentences with no wasted words. The main behavior is front-loaded, and the second sentence provides actionable routing guidance. The description earns its place without redundancy.

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 fully documented 8-parameter schema, an output schema, and comprehensive annotations, the description is complete enough. It explains the cross-product scope, the typical use case, and the path to sibling tools. Any remaining operational details like pagination and sorting are already documented in the schema.

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 100%, so the baseline is 3. The description does not add parameter-level guidance beyond what the schema already documents, such as filtering by domainName, autoRenewEnabled, subscriptionTypes, or subscriptionStatus. This is acceptable because the schema carries the burden.

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 states a specific verb and resource: it searches every subscription on the account across all products, and lists representative product types. It also distinguishes itself from product-specific siblings by positioning itself as the cross-product search and pointing to eurodns_ssl_get_subscription and its siblings for full records.

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?

It explicitly says to start here for an expiry review and to switch to product-specific subscription tools once the product is known. This gives the agent both a when-to-use and a clear when-to-use-an-alternative signal.

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