GET /licenses

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds nothing beyond that — no note on pagination defaults, result caps, or how the 18 filters combine. For a list endpoint with many filters and no output schema, that is a real gap.

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 with the resource, which is good. But the second sentence, "Generated from Snipe-IT OpenAPI operation licenses," is generator boilerplate that conveys nothing about behavior and occupies half the text.

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?

An 18-parameter listing tool with no output schema and no documented return shape needs more: pagination behavior (limit/offset semantics), default sort/order, or response envelope. None of that is present, leaving the definition inadequate for correct invocation.

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 83%, so the schema carries most of the parameter meaning and a baseline of 3 applies. The description contributes no additional semantics (e.g., how `search` interacts with `name`, or whether `deleted` and `maintained` combine), so it neither helps nor hurts beyond baseline.

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 verb and resource ("Return a listing of licenses"), so the basic operation is clear. However, it does nothing to distinguish this from the closely-named sibling `snipeit_list_licenses`, leaving an agent unable to choose between them from the text alone.

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 rather than `snipeit_list_licenses`, `snipeit_get_user_licenses`, or `snipeit_raw_request`. The only framing is the raw HTTP path, which is not actionable selection guidance.

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