Delete Manufacturing Resource

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

Annotations already indicate destructiveHint: true. The description adds 'This action is irreversible,' which reinforces the destructive nature and provides clarity beyond the annotation. It does not disclose additional behavioral traits like cascading effects or permissions, but for a delete operation this is adequate.

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?

The description is extremely concise with two sentences. The first sentence states purpose and irreversibility, the second provides a usage hint. There is no redundancy or unnecessary information.

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?

The description covers the main points (purpose, irreversibility, schema hint) but lacks guidance on distinguishing from generic delete tools like delete_resource. It also does not mention error scenarios or permissions. Given the output schema exists and parameters are simple, the description is minimally complete.

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?

Both parameters have clear descriptions in the input schema (100% coverage). The description does not add extra meaning beyond what the schema provides. Since schema coverage is high, a score of 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 clearly states 'Delete a resource' with the verb and resource, and notes irreversibility. However, it does not differentiate from sibling tools like delete_resource, which is a more generic delete. The title is specific to manufacturing resources, but the description lacks that specificity.

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 advises to call get_schema first to discover valid resource types, attributes, and relationships. This provides a clear usage guideline. However, it does not specify when not to use the tool or provide alternatives among siblings.

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