GET /accessories

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of pagination defaults, result caps, or whether the listing is paginated when limit/offset are omitted.

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?

Very short, but the second sentence ('Generated from Snipe-IT OpenAPI operation accessories') is boilerplate metadata that duplicates the title and does not earn its place. No waste beyond that, but also no front-loaded substance.

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?

No output schema exists, so the description should convey something about the shape of the listing or its pagination behavior, and it does not. For a 7-parameter endpoint in a large sibling set, the description leaves the agent without the context needed to use it confidently over the alternatives.

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 all 7 parameters (sort, limit, order, expand, offset, search, order_number) are already documented in the schema. The description adds nothing on parameter semantics, so the baseline of 3 applies.

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 restates the name and title: 'GET /accessories: Return a listing of accessories' adds no more than the tool name already conveys. It does not distinguish this tool from siblings such as snipeit_list_accessories or snipeit_gen_accessories_1, which appear to serve the same resource.

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?

No guidance on when to use this versus the several near-identical accessory-listing siblings, nor any prerequisites or exclusions. The agent gets no help choosing among ~10 accessory endpoints.

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