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

With no annotations, the description carries the full burden. It discloses useful behavior: it validates the subscription via reg_number before pricing, and enforces a business rule that the price is never below RRP. It omits auth requirements, error behavior when no subscription is found, and rate limits.

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?

A single front-loaded sentence with the verb first and no filler. Compact and readable, though it packs two operations (subscription check + price return) into one clause chain.

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?

An output schema exists, so return values need not be explained, and the core flow is covered. However, with no annotations the description should say more about failure modes (invalid reg_number, no subscription) and the RRP floor source to be fully actionable.

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, and it does: it explains that reg_number identifies the subscription to check and product_sku drives the catalog price. Both required parameters are given contextual meaning beyond their bare names.

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 names a specific verb (Quote) and resource (ITS renewal) and clarifies the mechanism: checking subscription by registration number and returning a catalog price for product_sku. This is clear enough to distinguish it from invoice/subscribe siblings, though it never explicitly names an alternative it is not.

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 implies usage (a pre-purchase renewal quote) but gives no explicit when-to-use or when-not guidance, and does not reference siblings like lookup_rrp, request_its_renewal_invoice, or subscribe_its_renewal that an agent would need to route between.

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