ListingsItems_putListingsItem

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

No annotations are provided, so the description must disclose behavior on its own. It indicates a remote create/full-update operation, but it does not explain that a full update may replace existing data, that authorization or prerequisites are needed, or what side effects occur beyond mutation. 'Not here' is cryptic and not actionable.

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 text is short, but 'Catalog entry.' and 'Runs in your Kuudo deployment, not here.' are ambiguous and provide little clear value. The final clause carries the useful meaning, so brevity is achieved at the cost of clarity.

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?

This is a mutating API operation with no annotations, no output schema, and an empty input schema. The description does not identify required identifiers or request body, response shape, error behavior, or destructive implications, leaving an agent without enough information to invoke it reliably.

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 zero defined properties with additionalProperties allowed, so schema coverage is nominally 100%, which sets the baseline at 3. However, the description adds no parameter meaning: it does not mention sellerId, sku, marketplaceIds, or the item body that a PUT listings item operation normally requires.

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 operation: 'Creates a new or fully-updates an existing listings item for a selling partner.' This is a specific verb and resource, and 'fully-updates' hints at PUT semantics compared with partial-patch tools, though it does not explicitly name sibling tools.

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?

There is no guidance on when to use this tool versus alternatives such as ListingsItems_patchListingsItem for partial updates or ListingsItems_deleteListingsItem for removal. The line 'Runs in your Kuudo deployment, not here' is an environment note rather than a concrete selection criterion.

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