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 conveyed structurally. The description adds a genuinely useful behavioral fact not in the annotations — the required 'vendors:write' scope — but says nothing about cascading effects on related records or irreversibility beyond what the annotations imply.

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, action front-loaded, zero filler. Every clause adds information (the operation, the key, the auth requirement) with no repetition of structured fields.

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 single-parameter delete with full annotation coverage and a fully documented schema, the description is nearly sufficient: it names the operation, the key, and the required scope. It leaves minor gaps around failure behavior for unknown IDs and whether related vendor records are affected, but nothing essential to invoking it is missing.

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?

There is only one parameter, and schema coverage is 100% with the schema itself documenting it as 'Vendor ID' with uuid format. The description's 'by ID' adds nothing beyond the schema, so the baseline 3 for a fully documented single parameter is appropriate.

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 ('Delete') and resource ('vendor') and the lookup key ('by ID'), so the action is unambiguous. It does not explicitly differentiate itself from siblings like delete_vendor_site_assignment or update_vendor, but the delete_* naming family makes the distinction reasonably clear.

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 (e.g., get_vendor to confirm the record, or delete_vendor_site_assignment for child records). Usage is only implied by the verb in the name, with no conditions, prerequisites for lookup, or exclusion criteria stated.

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