ruddur_create_marketplace_listing

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

The description goes beyond annotations by explaining server-side behavior: natural payload processing, top-level waypoint conversion, and assessmentConfig restrictions. It also states the required auth scope. It does not cover return values or errors, but annotations already flag the write nature.

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 front-loaded with the core action and then provides dense, purposeful constraints. Every sentence carries useful information, though the content-policy sentences form a long run-on that could be slightly more structured.

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 only two parameters, the description covers invocation essentials: payload handling, content restrictions, and required scope. It does not describe the response format, but that is not strictly necessary given the schema and annotations.

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?

Although the schema already describes the body/query parameters, the description adds crucial semantic guidance: natural fields can be passed top-level, tags are comma-separated, status/currency are lowercase, and assessmentConfig is only for assessment waypoints. This is valuable beyond the generic schema.

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 listing,' which clearly identifies the action and resource. The name and sibling context (update/delete/list listings) make the tool's purpose distinct without ambiguity.

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 provides explicit usage context: the required scope, accepted payload conventions, and content policy. It implies this is for creating new listings, but does not explicitly contrast with alternative sibling tools like update_marketplace_listing.

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