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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered; the description's 'without creating product or payment state' restates that in domain terms. It adds useful context about the catalog being immutable and returns being revision digests, but says nothing about pagination behavior for the cursor.

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 tight sentences with no waste, and the operation and scope are front-loaded. Nothing is padded, though the brevity comes partly at the cost of the missing parameter and pagination guidance.

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 safety profile is annotation-covered. However, for a paginated search tool the description omits how the cursor is meant to be used across calls, leaving a real gap for an agent driving multi-page retrieval.

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 0% top-level schema description coverage and three parameters, the description carries the burden but only implies the q parameter via 'free-text query.' The limit and cursor parameters are never mentioned, and while the cursor $def internally warns not to construct it, that is schema content, not description content.

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?

States a specific verb (Search) and resource (immutable Ausca offer catalog) with the query mechanism (free-text). This distinguishes it implicitly from the sibling ausca_get_offer, which retrieves a single offer, but the description never names that sibling to make the contrast explicit.

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?

Usage is implied by 'by free-text query' and 'Returns stable offer identities,' which hints at a search-then-fetch flow, but there is no explicit when-to-use guidance and no mention of the alternative ausca_get_offer for direct retrieval. The agent must infer the search-vs-fetch boundary itself.

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