GET /locations/{id}

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds no further behavioral context, such as error behavior for unknown IDs or what subset of a location record is returned; the 'Generated from Snipe-IT OpenAPI' line is provenance, not behavior.

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?

Two short sentences with the core purpose front-loaded and no padding beyond the generator-provenance note. It is a little redundant with the tool title but efficiently sized.

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?

There is no output schema and the description does not describe the returned location record, and it does not disambiguate the tool from its duplicate siblings. It is minimally adequate for a simple read-by-id call because the annotations carry the safety profile, but it leaves real gaps.

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?

The single id parameter has 0% schema description coverage. The phrase 'by id' only weakly implies it is a location identifier, and nothing says whether it is the numeric Snipe-IT location ID or some other key. With no schema text to compensate, the description should do more.

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?

States a specific verb and resource: 'Get location details by id'. That is clearer than the endpoint-style name alone. However, it never distinguishes this tool from the many sibling location getters (snipeit_get_location, snipeit_gen_locationsid, snipeit_gen_locations_2/_3), so an agent cannot tell which of the near-identical tools to call.

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 about when to use this tool versus the numerous other location-fetching siblings, and no prerequisites or exclusion criteria are given. The agent must infer usage from the name and path alone.

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