get_coupon

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't mention whether the coupon must exist, what happens if not found, whether it's a read-only operation, or any rate limits or auth requirements. The description is too thin to inform an agent about side effects or failure modes.

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 a single short sentence with no wasted words. It's front-loaded with the verb and resource. However, it's so brief that it sacrifices useful context.

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 tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. An agent doesn't know what 'details' includes, what the return format is, or how this differs from list_coupons. The tool is simple, but the description still leaves critical 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%, and the description doesn't explain what 'slug' or 'couponCode' mean or how they relate. The parameter names are somewhat self-explanatory, but the description adds no value beyond the schema, and the required combination of both parameters is unexplained.

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 clear verb ('Get') and resource ('details for a specific coupon'), which distinguishes it from list_coupons and create_coupon. However, it doesn't explicitly differentiate from update_coupon or other coupon-related tools, and 'details' is somewhat generic.

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?

No guidance on when to use this tool versus alternatives like list_coupons or get_book. The description implies a lookup use case but doesn't state when it's appropriate or what distinguishes it from sibling tools.

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