DELETE /fields/{id}

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond restating the operation and 'Generated from Snipe-IT OpenAPI operation' boilerplate — no mention of what cascade effects deleting a field has on associated asset values or fieldset links.

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 with the action front-loaded. The trailing 'Generated from Snipe-IT OpenAPI operation fieldsid-1' is provenance filler that doesn't help an agent, but overall it is not bloated.

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 destructive write with no output schema, the description should ideally note irreversibility or side effects on fieldsets/asset data. Annotations convey destructiveness and the schema covers both params, so the minimum is met, but the consequence of the delete is left unexplained.

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 coverage is 100% and the 'id' and 'confirm' parameters are fully documented in the schema, so the baseline applies. The description contributes no additional semantics about the id or the confirm gate beyond what structured data already provides.

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: 'Delete a custom field.' An agent can tell this is the destructive field-removal operation versus siblings like snipeit_gen_update_fields or snipeit_gen_fieldsid, though the description never names or contrasts those siblings explicitly.

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 guidance on when to use this versus alternatives, no prerequisites, and no warning that a GET of the same resource (snipeit_gen_fieldsid) exists. The only hint of usage context lives in the schema's 'confirm' parameter description, not the tool description.

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