POST /accessories

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, but the description adds nothing about consequences, required permissions, or reversibility of a destructive write. It also never mentions the `confirm` safety gate, which is exactly the kind of behavior an agent must know about before invoking a destructive call.

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?

It is short and front-loaded with the verb+resource, but the 'Generated from Snipe-IT OpenAPI operation accessories-1' clause is pure filler that consumes roughly half the text without informing the agent.

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?

A destructive nested-body create with ten undocumented fields, no output schema, and a confirmation mechanism deserves far more description. The agent has no idea what a successful response looks like or what the body requirements really mean.

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 only 50%, and the nested body defines ten fields (name, qty, category_id, etc.) with no meaning added by the description. Nothing explains field semantics, required-vs-optional intent, or how `confirm` interacts with SNIPEIT_CONFIRM_WRITES.

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 and resource ('Create a new accessory'), which is enough to know it is a create operation. However, with dozens of near-identical `snipeit_gen_accessories*` siblings, it offers no differentiation beyond the resource name, and the 'Generated from Snipe-IT OpenAPI operation accessories-1' tail adds no distinguishing information.

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 versus `snipeit_raw_request` or the other accessory endpoints, nor any prerequisite context. Usage is only implied by the word 'Create'.

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