Retrieve one offer

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

With no annotations provided, the description carries the transparency burden. It explicitly states 'Read-only,' which is important for an AI agent's safety assessment, and it describes the returned data (Features, pricing, Links). No contradictions or hidden side effects are suggested.

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?

Three short, purposeful sentences: what it does, safety property, and when to use it. Every sentence adds value and the key information is front-loaded.

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 single-offer retrieval with one required parameter, the description is complete enough: it covers the operation, the read-only nature, the main return contents, and the usage condition. Since there is no output schema, mentioning Features, pricing, and Links helps the agent understand expected results.

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 schema already fully documents offer_ref and customer_ref. The description adds little beyond 'by its reference' and does not explain the customer_ref direct-subscribe-link behavior, but the schema covers that detail adequately.

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: 'Retrieves a single ProAbono offer by its reference.' It also names what is included (Features, pricing, Links), which clearly distinguishes it from list_offers by emphasizing the singular, reference-based lookup.

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 sentence 'Use it when the offer reference is already known' gives explicit context for when to invoke this tool. It implies that list_offers is the alternative when the reference is unknown, though it does not name the sibling tool explicitly.

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