GET /fields

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — no mention of pagination, default page sizes, or what a 'field' entry contains, despite five paging/sorting parameters.

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 that are front-loaded, but the second sentence ('Generated from Snipe-IT OpenAPI operation fields-1') is codegen boilerplate that conveys little to an agent choosing a tool. Nothing is bloated, but very little is also said.

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 list endpoint with five optional query parameters and no output schema, the description should indicate what is returned and how pagination behaves. It says only that fields are 'available', leaving return shape and paging semantics undocumented.

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 all five parameters (sort, limit, order, offset, search) carry their own descriptions, so the schema does the heavy lifting. The description adds no extra meaning such as default sort column or whether search matches field name vs. type, so baseline 3 applies.

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 names the verb and resource ('GET /fields') and clarifies the payload as 'a listing of available custom fields', which is more informative than the bare name. However, it does nothing to distinguish this tool from the many near-identical siblings (snipeit_gen_fields, snipeit_gen_fields_2, snipeit_gen_fieldsets, etc.), leaving the agent unable to tell which one to pick.

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, when to prefer snipeit_gen_fields_2 or snipeit_gen_fieldsets, or what preconditions apply. The agent must infer everything from the name.

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