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 largely covered. The description adds the required authorization scope ('parts:write'), which is not present in the annotations and is valuable for an agent. It does not describe side effects, referential-integrity failures, or what happens to dependent records, but given annotation coverage this is a moderate gap.

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, front-loaded with the core action and followed by the prerequisite. There is no redundancy or filler; every sentence earns its place.

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 simple single-parameter delete tool with full schema coverage and annotations that already convey the destructive and idempotent nature, the description covers the essentials: what it does, how to identify the target, and the required scope. It could optionally note whether deletion fails when the part is referenced elsewhere, but that is a minor omission given the tool's simplicity.

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 the single parameter 'id' is fully documented in the schema as a UUID with a clear description. The description only restates that deletion is 'by ID,' adding no new semantic detail beyond the schema. With the schema doing the heavy lifting, a baseline 3 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?

The description states a specific verb and resource: 'Delete a part/inventory item by ID.' It clearly identifies the operation, but it does not explicitly distinguish this tool from siblings like delete_asset_part, delete_infrastructure_asset_part, or delete_part_category. An agent can infer the difference from the name, but the description itself offers no differentiation.

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?

The description includes a prerequisite ('Requires parts:write scope'), which gives useful context for when the tool can be used. However, it provides no guidance on when to choose this tool over alternatives, no exclusions, and no mention of conditions under which deletion might fail. Usage is implied rather than explained.

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