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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by indicating the tool is free, public, and pre-payment, which are behavioral traits beyond the annotations. It does not disclose pagination or result limits, but the annotation bar is lower.

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 extremely concise with two short sentences that both earn their place. The 'FREE DISCOVERY' label is front-loaded, and the core behavior is stated immediately without filler.

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?

For a simple optional-parameter search tool with safety annotations, the description provides basic context: free discovery of public metadata before payment. However, with no output schema and no parameter descriptions, an agent cannot fully predict return shape or filtering semantics. It is adequate but has clear gaps.

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 for lack of parameter documentation. It does not mention kind, query, or max_price_usd at all, leaving the agent with only property names and enum values to infer semantics. This is a clear gap.

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 clearly states the tool searches public offer metadata, which is a specific verb-resource combination. The 'before payment' qualifier distinguishes it from paid or Stripe-specific siblings like list_stripe_offers, though it does not explicitly name alternatives.

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 description gives clear usage context: use this for free discovery of public offer metadata before payment. It does not explicitly state when not to use it or name sibling alternatives, but the context is strong enough for an agent to infer the intended use case.

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