bookshelf_delete_qualityprofile

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

The annotations already declare destructiveHint=true and readOnlyHint=false. The description repeats 'DESTRUCTIVE: this deletes data' without adding new context such as irreversibility, cascading effects, or failure conditions. It adds minimal value beyond what annotations already provide.

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 very short (two sentences) and front-loaded with the core purpose. However, the second sentence redundantly repeats the annotation's destructive hint, slightly diminishing efficiency. Still, it is appropriately concise.

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?

Although the tool is simple (one parameter, output schema exists), the description lacks critical context for a destructive operation: it doesn't mention potential side effects (e.g., deleting a profile used by books), whether deletion is permanent, or any prerequisites. Annotations only signal destructiveness, not the full consequences. This is under-specified for such an impactful action.

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 0%, and the description does not explain the 'id' parameter beyond the obvious. It does not state that 'id' refers to the quality profile ID or provide any constraints (e.g., must exist). The single integer parameter is somewhat inferable from the tool name, but the description fails to explicitly document it.

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 'Delete qualityprofile' clearly indicating the action (delete) and resource (qualityprofile). It distinguishes this tool from siblings like create, update, get, and list qualityprofile 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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, no exclusions (e.g., cannot delete default profile). The description simply states the action and a generic warning, leaving the agent to infer usage.

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