ruddur_delete_marketplace_listing

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds the required OAuth scope 'marketplace.manage', which is not present in structured data, and the delete action is consistent with the destructive hint.

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 with one key behavioral note (scope), containing no redundant information. It is front-loaded with the primary action.

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 delete operation with one required identifier and confirmation flag, the description is minimal but lacks any warning about side effects (e.g., related licenses/coupons). The output schema is absent, so return behavior is not described; however, the tool's simplicity may not demand more.

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 already provides descriptions for all four parameters (pathParams, body, query, confirm), with confirm behavior clearly specified. The tool description does not add further parameter semantics beyond what the schema states.

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 uses the specific verb 'Delete' with the resource 'marketplace listing', clearly identifying the operation. It distinguishes from sibling tools like ruddur_update_marketplace_listing or ruddur_list_my_marketplace_listings.

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?

It does not explicitly state when to use this tool versus alternatives, though the delete verb implies the use case. It does include a prerequisite (scope: marketplace.manage) but no exclusions or alternative recommendations.

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