GET /locations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond restating that this is a GET/list operation, and it does not explain pagination behavior, filtering expectations, or response shape.

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 short and front-loads the operation, but the second sentence, "Generated from Snipe-IT OpenAPI operation locations," is boilerplate that adds little operational value. It is concise but under-specified rather than information-dense.

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 a tool with 11 optional parameters, no output schema, and many sibling location endpoints, the description is too thin. It does not explain how filtering, search, sorting, or pagination should be used, leaving the agent to infer behavior from parameter names alone.

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?

There are 11 parameters and only 45% schema description coverage. Six filter parameters (zip, city, name, address, address2, country) have no descriptions anywhere, and the description adds no parameter semantics to compensate. An agent gets no help understanding how to use these filters.

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: "List locations." That is clear enough for an agent to understand the core operation, but it does not distinguish this tool from the many sibling location tools such as snipeit_list_locations, snipeit_gen_locations_1, or snipeit_get_location.

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 gives no guidance on when to use this tool versus alternatives. It does not mention filtering, pagination, or why an agent would choose this generated endpoint over snipeit_list_locations or the other location-related siblings.

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