ruddur_create_coupon

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

The description adds a useful behavioral constraint—the required 'marketplace.manage' scope—beyond the annotations. It does not contradict the annotations (readOnlyHint false, etc.) and provides authentication context that annotations lack.

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, front-loaded with the primary purpose, and then provides the most essential extra details (aliases and scope). Every sentence earns its place with no filler or redundancy.

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 create tool with no output schema and generic body schema, the description offers the core purpose, some field names, and a scope requirement, but it does not state which aliases are required, how they should be structured, or what the response looks like. This is a minimal viable description with clear gaps for reliable invocation.

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 input schema only describes generic 'body' and 'query' parameters, while the description contributes domain-specific coupon aliases like promoCode, percentOff, and marketplaceListingId. However, the list is incomplete ('such as') and omits types/requiredness, so it adds meaning but not full semantics.

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 opens with 'Create a marketplace coupon,' which is a specific verb+resource statement that clearly differentiates this tool from siblings like ruddur_update_coupon and ruddur_list_coupons. It leaves no ambiguity about what operation is performed.

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 explicit alternatives are mentioned, but the create action and the prerequisite 'Requires scope: marketplace.manage' give implied usage context. It lacks guidance on when to use this instead of update or list, so it does not fully address when/not/alternatives.

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