Remove C4D Entity

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add one useful behavioral trait: the deletion is 'wrapped in an undo step,' implying reversibility. However, it does not disclose side effects such as whether deleting an entity cascades to children, associated data, or dependent references.

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: the action 'Delete' comes first, followed by the object and a brief parenthetical about undo behavior. Every word contributes meaning, and there is 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 tool with a complex polymorphic handle schema and no annotations or output schema, the description is too thin. It omits guidance on when to choose this tool over related removal tools, what side effects to expect, and how the entity resolution works. An agent would need to infer most operational context from the schema and sibling names.

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%: the handle parameter is described as 'Entity to delete' and its schema enumerates the supported entity kinds. The description's phrase 'resolved entity' adds mild semantic value by indicating that the handle is resolved to an entity, but it does not go beyond what the schema already conveys.

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 states a specific action ('Delete') and a resource ('the resolved entity'), making the core purpose clear. It is not a tautology and adds the 'resolved' qualifier, which hints at how the handle works. However, it does not explicitly distinguish this from sibling removal tools like remove_graph_node or remove_xpresso_node, so it falls short of a 5.

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 about when to use this tool versus the many sibling tools that also remove or delete things, such as remove_graph_node, remove_user_data, or delete_track. The description simply says what the tool does, leaving the agent to infer appropriate usage from the tool name and context.

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