List accessories

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds that it is a 'paginated list' and 'supports search and common filters,' which is useful behavioral context beyond the annotations, but it does not elaborate on pagination mechanics, rate limits, or return format.

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 two short sentences, front-loaded with the endpoint and primary function. It is efficient and easy to parse, though it could be slightly more structured by explicitly separating purpose and capabilities.

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?

With 8 parameters and no output schema, the description is too brief to fully equip an agent. It omits important details like the behavior of the 'all' parameter (auto-pagination with truncation) and the fact that filter parameters may have unverified server-side support, which are critical for correct invocation.

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 75%, so some parameters (e.g., search, offset) lack schema-level descriptions. The description mentions 'search' and 'common filters,' providing minimal additional meaning, but it does not clarify the undocumented parameters or detail filter behavior.

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 (GET) and resource (accessories), making the core purpose clear. It does not, however, differentiate this tool from sibling list tools like snipeit_list_hardware or snipeit_search_hardware, which is why it falls short of a 5.

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 offers no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or exclusions that would help an agent choose between this and other list or search tools.

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