snipeit_locations_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'List all locations' and omits details like pagination behavior, default limits, authentication requirements, or whether the 'all' claim is affected by the limit and offset parameters.

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 a single short sentence with no wasted words, and the primary action is front-loaded. It is concise, though it may be too terse given the number of parameters and lack of other documentation.

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 five optional parameters, no output schema, no annotations, and only a one-line description, the tool is not fully specified. An agent would lack critical information about filtering, pagination, result shape, and how this tool relates to sibling location tools.

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 0%, yet the description gives no explanation of the five parameters. Parameter names like sort, limit, order, offset, and search are somewhat self-explanatory, but the description adds no meaning about accepted values, defaults, or how they interact.

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 'List all locations' uses a specific verb and resource, making the core operation clear. It is distinguishable from sibling tools like snipeit_locations_get and snipeit_locations_assets by the resource and action, though it does not explicitly differentiate them.

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 snipeit_locations_get or snipeit_locations_assets. The description provides no context for choosing it over other list tools or related location endpoints.

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