ebay_rename_store_category

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

The description adds substantial behavioral detail beyond the readOnlyHint=false annotation: it explains the asynchronous return (taskId, location), the polling workflow, the concurrency constraint (only one store category change at a time), and the required eBay Store subscription with sell.stores scope. This gives the agent everything needed to understand side effects and prerequisites.

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 purpose and API call, then flows into operational details. It is somewhat dense but every sentence adds value, with only the brief 'Pass the store categoryId and the new categoryName' sentence being marginally redundant given the schema descriptions.

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 an asynchronous mutation tool with no output schema, the description covers the return shape, polling mechanism, concurrency limits, and subscription requirement. An agent has all the information needed to invoke and follow up 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?

Schema description coverage is 100%, so the input schema already documents categoryId and categoryName thoroughly. The description repeats the parameter names but adds no new syntax, format, or edge-case information beyond what the schema provides, so a baseline 3 is appropriate.

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 states a specific verb ('Rename') and resource ('one custom eBay Store category'), and explicitly names the underlying API operation. It is clearly distinguishable from sibling tools like ebay_add_store_category, ebay_move_store_category, and ebay_delete_store_category.

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 clear context for usage: it is asynchronous, requires polling with ebay_get_store_task, and is subject to a one-change-in-flight constraint. It does not explicitly name alternative tools or state when not to use this one, but the verb and constraints make the appropriate context inferable.

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