IndividualClassesDelete

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

Annotations already mark destructiveHint=true, but the description goes beyond this by warning the user, stating that the class is removed, and noting that client-side approval is required. That approval requirement is non-obvious operational context not conveyed by the annotations.

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 short, front-loaded with the action, and adds a warning and an approval requirement without filler. The slight redundancy between 'Destructive' and 'removes' is acceptable given the placed emphasis.

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 single-parameter delete tool, the description plus annotations and schema provide everything needed: what is deleted, that it is destructive, that client-side approval is required, and which classId to provide. No output schema is present, so return-value detail is not required.

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 only parameter classId fully with 'integer (optional)', and the description adds no additional meaning. Given 100% schema description coverage, 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?

States the specific operation 'Delete' and the resource 'an individual class', which clearly distinguishes the tool from siblings like GroupClassesDelete. Even without the name, the description identifies exactly what it acts on.

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 the tool is for deleting individual classes, and the sibling list includes GroupClassesDelete and IndividualClassesCreate/GetList, so context exists. However, it does not explicitly state when to use this tool versus alternatives or mention exclusions.

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