Delete Generic Tool Item

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

The description repeats 'cannot be undone' twice, which aligns with the destructiveHint annotation. However, it does not add new behavioral insights beyond what annotations already provide (readOnlyHint, destructiveHint, idempotentHint). No mention of authorization requirements or response behavior.

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 front-loaded with the core action but includes redundant phrasing (e.g., 'permanently delete' and 'cannot be undone' repeated). It is functional but could be more concise without losing clarity.

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 delete operation with well-documented parameters and annotations, the description covers the essentials (required params, endpoint, link to docs) but omits details about the optional view parameter, error scenarios, and response format. It is adequate but not thorough.

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%, so the baseline is 3. The description lists the three required parameters but does not enhance their meaning beyond the schema. The optional 'view' parameter is not mentioned, but that is acceptable given the baseline.

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 the action (Delete) and the resource (Generic Tool Item). It also specifies it pertains to 'Custom - Configurable Tools', which helps distinguish it from other delete operations among the many sibling 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 indicates when to use this tool (to permanently delete custom configurable tools) and lists required parameters, but it does not explicitly contrast with alternatives or mention when not to use it. Sibling tools like delete_generic_tool_status exist, but no guidance on choosing between them is provided.

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