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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the agent knows this is a destructive write. The description's one genuinely additive fact is the cascade: portrait/library images are deleted too. It stops short of stating irreversibility, required permissions, or behavior when the influencer does not exist.

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?

One sentence, front-loaded with the action and resource, with the cascade scope appended rather than buried. There is no filler or restatement of the title.

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 destructive delete with no output schema, annotations already carry the safety profile and the description adds the important cascade-deletion detail. It is nearly complete; only irreversibility and not-found/error behavior are unaddressed, which is a minor gap for this complexity.

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%, so the description carries some burden, but the single parameter 'influencerId' is self-explanatory and the schema supplies type/format/pattern (UUID) plus the required constraint. The description adds nothing about the identifier, which is acceptable but not additive.

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?

Specific verb ('Delete') plus specific resource ('an AI influencer'), with an added scope clause naming the collateral data ('its stored portrait/library images'). This cleanly separates it from the other delete_* siblings (delete_content_piece, delete_content_source, delete_clone_job), which target different resources.

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 never says when to use this tool versus alternatives such as regenerate_influencer, nor does it state prerequisites or exclusions. The only implicit guidance is that this is the removal path for an influencer, which the agent must infer from the verb.

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