get_offer_item

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'Read-only', which indicates no side effects, but omits critical details such as error handling (e.g., if DPS ID is invalid), authentication requirements, or return format. This leaves significant gaps for a simple lookup tool.

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: two short sentences that front-load the core purpose. Every word earns its place with no redundancy or unnecessary detail.

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?

Given the tool's low complexity (single object retrieval), no output schema, and no annotations, the description is minimally adequate. It could improve by stating what is returned (e.g., 'Returns the full offer item object') or how errors are handled, but for a basic lookup it provides enough to start.

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. It mentions 'DPS ID' but does not explicitly map it to the 'offer_id' parameter, and the 'access_token' parameter is entirely unexplained. The description adds minimal semantic value beyond the schema.

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 action ('Look up'), the resource ('a single offer item'), and the identifier ('by its DPS ID'), effectively distinguishing it from sibling tools like 'list_offer_items' (listing multiple) and 'update_offer_item' (modification).

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 'Read-only' implies this tool is for retrieval without side effects, setting clear context. However, it does not explicitly state when to use it versus alternatives like 'list_offer_items' or 'update_offer_item', though the distinction is inferable.

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