ruddur_list_coupons

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds the scope requirement, which is an authentication behavior not covered by annotations. However, it does not describe pagination, filtering, or response format, so it adds limited behavioral context beyond annotations.

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 short sentences, front-loaded with the purpose, and every word adds value. There is 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 generic schema (only body/query) and no output schema, the description is too sparse. It does not explain what query parameters or body fields mean for this specific tool, nor what the response will look like. The only concrete context is the purpose and scope requirement, leaving the agent uncertain about how to invoke the tool correctly.

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 has generic 'body' and 'query' parameters with 100% description coverage, but these descriptions are generic to all tools and not specific to coupons. The tool description adds no parameter meaning. Furthermore, the body schema mentions POST/PUT/PATCH operations, which is inconsistent with the read-only nature of a list tool, undermining clarity.

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 'List creator marketplace coupons' clearly states a specific verb (List) and resource (creator marketplace coupons). It also specifies required scopes, which adds clarity. This distinguishes it from sibling tools like ruddur_create_coupon and ruddur_update_coupon.

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 provides no guidance on when to use this tool versus alternatives. It only mentions required scopes, which is a prerequisite rather than usage guidance. There is no mention of alternative tools or conditions under which this list operation is preferred.

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