POST /fields/{id}/associate

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is known from structured data. The description adds nothing beyond those hints: it doesn't say an association persists server-side, whether re-running duplicates, or what the confirm="YES" write gate means in practice. Only the boilerplate 'Generated from ... OpenAPI operation' sentence is added.

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 action, which is good, but the second sentence ('Generated from Snipe-IT OpenAPI operation fieldsidassociate') is pure provenance noise that consumes half the text without helping an agent invoke the tool.

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?

This is a destructive, non-idempotent mutation with a nested body object and no output schema; the description should at minimum explain the effect of the association and the confirm gate. Neither is covered, leaving the agent to infer everything from annotations and the schema.

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 67% and the description supplies no parameter semantics at all — the meaning of id, body.fieldset_id, and the confirm gate is left entirely to the schema. It does not compensate for the partially undocumented body object.

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 specific verb (Associate) and both resources (custom field, custom fieldset), which is more than a restatement of the opaque generated name. However it does not differentiate from the closely named sibling snipeit_gen_fieldsiddisassociate or clarify what association means relative to snipeit_gen_update_fields, so an agent still needs the schema to reason about it.

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 guidance, no preconditions, no mention of the alternative disassociate operation. The only routing signal is the name itself; the description never says whether this is additive (field may belong to multiple fieldsets) or replacing.

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