nominations_delete_instance

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. 'DELETE' implies a destructive, likely irreversible mutation, but there is no statement about permissions, confirmation requirements, side effects on related resources, or error behavior for a nonexistent id.

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, but the parenthetical repeats the exact same string verbatim, so the entire second half is pure waste rather than information. Structure is technically front-loaded, yet the content is too thin to be considered efficient communication.

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 operation with no annotations, no output schema, and no surrounding documentation, the description is not complete enough. An agent gets no confirmation of consequences, auth requirements, or what a successful delete returns.

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% for the single id parameter, so the schema already documents it ('the id of the requested resource'). The description adds no syntax, format, or ID-type detail, which is the expected baseline of 3 when the schema does the work.

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 is the REST path 'DELETE /v1/nominations/{id}', which is essentially a restatement of the tool name nominations_delete_instance rather than an explanation of what deleting a nomination means. It does convey the HTTP verb and resource, so a sibling like nominations_get_instance is distinguishable, but no purpose beyond the name is added.

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 versus nominations_get_instance, nominations_update_instance, or any related sibling, nor any stated preconditions. The path alone implies 'use this to delete by id', but nothing is explicit.

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