remove_actor

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

With no annotations, the description carries the transparency burden. It discloses a critical side effect: automatic removal of ECE rules that reference the actor. However, it does not mention permanence, error behavior, or authorization requirements, though the cascade is well highlighted.

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, focused sentence that states the primary action and the key side effect. Every word contributes meaning, with no unnecessary filler.

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 one-parameter delete tool with an output schema, the description is largely complete. It covers both the action and its cascade effect. The only minor gap is not stating that the actor must exist, but that is implied by a delete operation.

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 description provides no additional meaning for 'actor_id'. It does not explain how to obtain this ID or any constraints, leaving the parameter under-explained despite its simple name.

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' with a resource 'actor' and adds a key differentiator: 'automatically remove ECE rules that reference it.' This clearly distinguishes it from sibling tools like update_actor and create_actor.

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 usage is implied by the verb 'Delete', but there is no explicit guidance on when to use this tool versus alternatives, nor any mention of restrictions or prerequisites. The description lacks exclusions such as what happens if the actor doesn't exist or if rules reference it in a complex way.

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