delete-crm-object-schemas-v3-schemas-objtype_objtype

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

No annotations exist, so the description must carry the transparency burden. 'Delete a schema' only names the action, without disclosing irreversibility, scope of deletion, required permissions, or side effects on associated data or properties.

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 extremely concise and front-loaded with the verb. It wastes no words, though the extreme brevity edges toward under-specification, so it earns a 4 rather than 5.

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 destructive schema deletion with no annotations or output schema, the description provides none of the necessary contextual details—such as reversibility, data impact, permissions, or required state (e.g., archived). It is minimally informative and insufficient for an agent to reason about consequences.

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 100%, so the baseline is 3 per the rubric. However, the description itself adds no parameter context; the 'archived' parameter seems semantically odd for a delete (description says 'return results') and the tool description does not clarify its role.

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 uses a specific verb 'Delete' and resource 'a schema', clearly indicating the operation. It broadly distinguishes from sibling tools, though it doesn't specify whether it deletes a schema definition versus associations or object instances.

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 is provided on when to use this tool versus alternatives. The sibling list contains many delete operations (objects, associations, properties, schema associations), but the description offers no exclusions, prerequisites, or preferred context.

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