Delete a creator

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

The description adds key behavioral details beyond annotations: it records a cross-device delete to prevent reappearance, clarifies that ads rendered with the person remain untouched, and notes that the portrait can be saved again. These are not covered by annotations (which only mark destructive/idempotent), so they add significant context.

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?

Two sentences, front-loaded with the action, then efficient details about scope and re-save. No wasted words.

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 single-parameter delete tool with annotations covering destructive/idempotent, the description covers cross-device behavior, side effects (ads untouched), and reversibility (save_creator). There is no output schema, so return values are not a concern. An agent has all needed info to call correctly.

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 schema already describes the 'id' parameter as the creator id from list_creators, and the description repeats that without adding new details. Since coverage is 100%, the description adds no extra semantic value beyond the schema.

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 verb ('Remove') and resource ('saved creator from this workspace’s cast'), and identifies the id source ('from list_creators'). It clearly differentiates from siblings like save_creator by focusing on deletion and scope.

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 description says the deletion only drops the roster entry and that the same portrait can be saved again with save_creator, implying the alternative for re-adding. It also notes no confirm is needed, providing a usage cue. It could be more explicit about when not to use it (e.g., if wanting to fully remove permanently), but it gives clear context.

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