delete_content_type

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

The description only says 'delete', implying irreversibility, but does not disclose any behavioral traits such as cascading effects, permission requirements, or safety measures. No annotations are provided to supplement this information.

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 sentence, which is concise, but it may be too brief for a deletion operation. It lacks structure and does not efficiently convey important information that the schema does not cover.

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?

Given the lack of annotations and output schema, the description is insufficiently complete. It does not specify what happens after deletion (e.g., confirmation, impact on entries), nor does it provide any usage context beyond the basic action.

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 input schema has 3 parameters with 67% description coverage (spaceId and environmentId have descriptions, contentTypeId does not). The tool description does not add any meaning beyond the schema; it does not explain the purpose of each parameter or how to form valid values.

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 'Delete a content type' clearly states the action and resource. It distinguishes from siblings like create_content_type and get_content_type, providing a clear purpose. However, it lacks any extra context such as scope or constraints.

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. There is no mention of prerequisites, side effects, or when not to delete. The sibling tools include other delete operations, but no differentiation is given.

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