Delete Quality Profile

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

Discloses destructive action and confirmation requirement, but with no annotations, the description should provide more context (e.g., irreversibility, success/error behavior). It meets a minimal standard.

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?

Single sentence with no fluff. Concise and to the point.

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?

Given 15 parameters and no output schema, the description is severely incomplete. Fails to explain most parameters, expected return, error states, or permanence of deletion.

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 coverage is 0%; description only indirectly addresses 'id' and 'confirm'. The other 13 parameters, many seemingly irrelevant (e.g., app, body, page), are unexplained. Adds little beyond schema constraints.

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?

Clearly states verb 'delete' and resource 'quality profile', with identifier 'id'. Distinguishes from sibling tools like create, update, clone, and get.

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?

Mentions requirement 'confirm=true', which is a precondition. However, no explicit guidance on when to use versus alternatives, and no warning about destructive nature beyond the confirm requirement.

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