Check if a ClickBank order is active

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

Annotations already declare readOnlyHint and openWorldHint, so the bar for additional disclosure is lower. The description adds meaningful behavioral details beyond annotations: it explains the value mapping (active=true/false) and the 403 response semantics, including the case where the receipt is missing or inaccessible.

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 two sentences with no filler. It front-loads the core purpose and status conditions in the first sentence, then clarifies error mapping in the second, making every word useful.

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 single-parameter, read-only tool with no output schema and annotations covering safety, the description fully covers what an agent needs: the exact boolean semantics, the statuses that determine falseness, and the HTTP 403 behavior. No critical calling information is missing.

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?

The schema fully describes the only parameter (receipt) as a ClickBank receipt ID, so schema coverage is 100%. The description does not add additional meaning to the parameter itself beyond confirming it receives a receipt, meeting the baseline but not exceeding it.

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's function: it checks whether an order is active by evaluating refund, chargeback, and cancellation status. It distinguishes itself from sibling tools like get_order and list_orders by focusing specifically on the active/inactive boolean outcome rather than order details or lists.

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 implies use for a quick status check via HEAD, but it does not explicitly state when to use this over alternatives like get_order or when not to use it. There are no exclusions or alternative tool references, leaving usage context to inference.

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