parse_delete_class

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

With no annotations, the description fully carries the behavioral disclosure burden. It explicitly states the operation is permanent ('Elimina permanentemente'), irreversible ('Esta operación es irreversible'), and requires a master key. It also clarifies that ALL objects of the class are deleted, which is a critical destructive behavior.

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 a single, front-loaded sentence that conveys the essential action and consequences. Every word earns its place, with no redundant or filler content.

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 simple 1-parameter destructive tool with no output schema, the description covers the main points: action, scope (all objects), irreversibility, and auth requirement. It does not mention error handling or return value, but these are less critical for a class deletion operation. The description is nearly complete for the tool's context.

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 tool description does not mention the className parameter. It only refers to 'una clase' without specifying how to pass it. The description does not compensate for the lack of parameter documentation, leaving the parameter semantics entirely to the schema, which is minimal.

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 clearly states the action: 'Elimina permanentemente una clase y TODOS sus objetos de Parse Server' (permanently deletes a class and ALL its objects). It uses a specific verb and resource, and distinguishes from siblings like parse_delete_field and parse_delete_object by indicating class-level deletion.

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 provides clear context for when to use the tool: to delete an entire class and all its objects. It mentions the prerequisite 'Requiere master key' (requires master key), implying high privilege. It does not explicitly name alternatives, but the scope is clear enough for an agent to infer this is not for deleting individual fields or objects.

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