TeachersDelete

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description is consistent with them. It adds meaningful operational context by explicitly warning that the teacher is removed and that client-side approval is required, which goes beyond what the annotations alone convey.

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 contains a clearly emphasized warning. The phrase 'removes the teacher' is somewhat redundant with 'Delete a teacher', but the warning format and approval note are still valuable and keep the description tight.

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?

This is a destructive call with only one parameter, yet the schema marks teacherId as optional and the description never clarifies that an ID is presumably required. There is no output schema, so the description also leaves the agent uninformed about the result or failure behavior of the operation.

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 sole parameter teacherId is self-explanatory by name, and schema coverage is 100%, so the schema carries the descriptive burden. The tool description does not clarify whether teacherId is actually required, but the parameter name and type provide enough baseline semantic meaning.

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 a specific verb ('Delete') and resource ('a teacher'), making the operation unambiguous. It naturally distinguishes itself from sibling tools like TeachersGetList, TeachersUpdate, and TeachersCreate without needing extra explanation.

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 does not say when to use this tool versus alternatives such as TeachersUpdate or TeachersGetDetail. The warning about destructiveness is useful, but there is no explicit guidance on prerequisites, when not to use it, or which sibling to choose instead.

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