GET /fieldsets

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 nothing behavioral beyond that: no mention of pagination defaults for limit/offset, whether results are paginated at all, or the shape of the response. The 'Generated from Snipe-IT OpenAPI operation fields' sentence is provenance metadata, not behavioral context.

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?

Very short and front-loaded with the endpoint and purpose. The trailing clause about codegen provenance is low-value filler, but it costs only a few words.

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?

With no output schema, the description should say something about what a fieldset record contains or how results are paged, and it does neither. Annotations cover the safety dimension, so the gap is moderate rather than severe, but for a list tool in a large confusing sibling set it should disambiguate more.

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 100%, and each of the five parameters (sort, limit, order, offset, search) carries its own description, so the baseline is 3. The description adds no filtering or sorting semantics beyond the schema, and notably does not clarify the search field's scope for this resource.

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: 'List all custom fieldsets'. That is clear enough to know what it returns. However, the sibling set contains snipeit_gen_fieldsets and snipeit_gen_fieldsetsid, and the description does nothing to distinguish this 'fields' endpoint from the nearly identically named 'fieldsets' tool, leaving real ambiguity.

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 versus snipeit_gen_fieldsets, snipeit_gen_fieldsetsid, or snipeit_gen_fields_2, all of which appear adjacent in the sibling list. No prerequisites, no exclusions, no note that it is a plain unpaginated list.

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