GET /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 safety is covered structurally. The description adds nothing behavioral beyond a provenance note ("Generated from Snipe-IT OpenAPI operation users") – no pagination defaults, no note that 29 optional filters all AND together, no 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?

It is short and front-loaded, but the leading "GET /users:" merely repeats the title and tool name, and the provenance sentence consumes a third of the text without informing the call.

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 29-parameter list endpoint with no output schema and no annotations explaining shape, the description omits everything an agent needs: filter interaction, pagination semantics, and returned fields. It is inadequate for the tool's complexity.

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?

With 29 parameters and only 52% schema description coverage, several filters (zip, email, state, country, start_date, end_date, username, first_name, last_name, group_id, company_id, location_id, department_id, employee_num) are undocumented in both schema and description. The description gives no hint about how filtering, sorting, or the limit/offset pair behave, so it fails to compensate for the coverage gap.

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?

It states a concrete verb and resource ("List users"), so the basic action is clear. But it does nothing to differentiate itself from the many close siblings such as snipeit_list_users, snipeit_gen_users_2, snipeit_gen_users_3 and snipeit_get_user, which an agent could not choose between from this text.

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 when-to-use guidance, no statement of what distinguishes this generated endpoint from the hand-written list/get user tools, and no mention of prerequisites or exclusions. The agent is left to infer everything.

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