delete_metaobject

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

With no annotations, the description must carry the full burden of behavioral disclosure. 'Delete a metaobject' merely restates the tool name and provides zero information about irreversibility, required permissions, cascading effects, or confirmation steps. It adds no behavioral context beyond the literal operation.

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 short, but this is under-specification rather than concise effectiveness. It lacks any structured information that aids the agent. While it avoids fluff, it fails to include essential details.

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?

The tool has no output schema and no annotations, and the description provides only minimal context. Given the complexity of the system with many sibling delete tools, this description is insufficient for an agent to understand the full implications or requirements of the operation. It needs more context about the metaobject resource and deletion semantics.

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 one parameter 'id' with a description 'Metaobject ID', providing 100% coverage. The tool description does not add any further semantic detail, but since the schema already fully documents the parameter, the baseline of 3 is appropriate.

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 metaobject' uses a specific verb and resource, clearly identifying the action and target. It distinguishes from siblings like delete_metaobject_definition or delete_product because it explicitly references 'metaobject'. However, it lacks additional context about the scope or kind of metaobject.

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 (e.g., metaobject existence), side effects, or situations where another delete tool might be more appropriate. The description offers no usage context.

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