Delete Tool

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

The annotations already declare this as destructive (destructiveHint=true), and the description adds no extra behavioral context. It does not mention whether deletion is permanent, cascades to associated resources, or requires specific permissions. The openWorldHint is also left unexplained, which is a gap for a destructive operation.

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 a single, concise sentence with no extraneous words. It directly states the action and target, perfectly sized for a simple one-parameter tool.

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, the description is adequate but not fully complete. It does not address potential side effects, return values, or the meaning of openWorldHint, which could be relevant for an agent deciding whether to invoke it. The annotations cover destructiveness, but the broader impact remains unclear.

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?

The schema covers the parameter completely with a description 'The tool id to delete' (100% coverage). The description's 'by id' merely repeats what is already in the schema, adding no new semantic meaning. 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 uses the specific verb 'Delete' with the resource 'tool' and identifies the method 'by id'. This clearly differentiates it from sibling CRUD tools like create, update, get, and bulk_delete_tools.

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 implies usage for deleting a single tool when its id is known, but it does not explicitly mention alternatives like lyzr_bulk_delete_tools or conditions where deletion should not be performed. No exclusions are provided, but the usage context is reasonably clear from the verb and parameter.

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