delete_class

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

With no annotations, description reveals that deletion actually nulls the entry, which is helpful. But lacks details on side effects (e.g., impact on actors using the class), reversibility, or error cases.

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, no redundancy. Action verb comes first, achieving front-loading and efficiency.

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?

Basic info for a delete operation with one parameter. Missing return value description (e.g., success/error) and any context about error handling or expected behavior.

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 100% and already describes the 'id' parameter as 'Class ID to delete'. Description adds 'by ID' but no additional meaning beyond the schema.

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 'Delete a class by ID' with specific verb and resource. The parenthetical '(sets entry to null)' clarifies the exact effect, distinguishing it from update_class or get_class.

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?

No guidance on when to use versus alternatives like delete_actor or update_class. Missing prerequisites (e.g., class exists) and conditions for safe use.

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