get_discount

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

With no annotations, the description carries full burden. It discloses that the tool returns 'type, amount, usage limits, and expiry' but does not explicitly state it is a read-only operation, nor does it mention any side effects, permissions, or rate limits. Adequate for a simple get operation but lacks depth.

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 sentence, which is concise, but it includes the unnecessary prefix '[WPCafe Pro]' which adds noise. The structure is acceptable but could be cleaner.

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 parameter-less output retrieval, the description gives a reasonable overview of what is returned. However, missing output schema means the agent cannot infer the exact structure, and no mention of error handling or edge cases. Adequate but not comprehensive.

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 coverage is 100% for the single 'id' parameter. The description adds value by explaining what details are retrieved (type, amount, usage limits, expiry), providing context beyond the schema's simple 'Discount ID' label.

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 retrieves details of a single discount code, differentiating it from siblings like list_discounts (multiple) or create/update/delete (mutations). However, it does not explicitly contrast with sibling tools or specify when to use this over others.

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 vs alternatives. The description does not mention any prerequisites, exclusions, or contexts where this tool is preferred over, e.g., list_discounts or create_discount.

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