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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is established. The description adds meaningful context beyond annotations: this is a free/preview operation that deliberately does not reveal paid content, only the expected shape. No contradiction with annotations exists.

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 very short and the main function is front-loaded. 'FREE QUALIFICATION' is slightly cryptic and could be clearer, but the description earns its length by conveying both the free access nature and the non-revealing behavior concisely.

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?

The tool is simple: one required parameter, no output schema, and read-only annotations. The description covers the core behavior but leaves the meaning of 'id' unspecified, so an agent cannot fully determine what value to pass. Given the low complexity, this is a minimal viable definition with a notable gap.

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 carries full responsibility for explaining the 'id' parameter. It does not explain what id refers to, such as an offer ID, request ID, or fulfillment ID. The agent must infer this from context and sibling tools, which is insufficient for confident invocation.

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 action ('Shows expected result shape') and a clear resource ('result or fulfillment schema'), and adds the key qualifier 'without revealing paid content.' It is clear about what the tool provides, though it does not explicitly differentiate from siblings like check_requirements or execution_preflight.

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 phrase 'FREE QUALIFICATION' hints that this tool is intended as a no-cost way to preview schema shape before committing to paid content, and 'without revealing paid content' implies a filtering behavior. However, there is no explicit statement of when to use this tool versus alternatives, nor any exclusions or preferred sibling comparisons.

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