GET /consumables/{id}/users

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds nothing — not what the endpoint returns, not pagination, not whether it lists users who checked out the consumable versus all users.

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 no padding, and the route appears first. It is concise but only because there is almost no content; the generator suffix sentence is pure noise.

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 must convey what is returned — a list of users tied to the consumable — and it does not. For a one-parameter read tool the burden is small, but the definition still leaves the agent guessing at the response shape and semantics.

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 required parameter 'id' has 0% schema description coverage. The path snippet implies it identifies a consumable, but neither the description nor the schema states that explicitly or clarifies what kind of consumable id is expected.

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 simply restates the HTTP route 'GET /consumables/{id}/users' plus a generator provenance note. It implies a read of the users associated with a consumable, but 'get_new-endpoint' is an auto-generated artifact name that conveys nothing and no sibling differentiation is offered.

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 when-to-use, when-not-to-use, or alternative is mentioned. With siblings like snipeit_gen_consumablesid, snipeit_gen_consumablesidcheckedout, and snipeit_gen_get_new_endpoint_consumables_id_user, an agent has no basis to pick this one.

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