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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description never explains what is destroyed — i.e., that existing stored copy is replaced/overwritten, and whether the prior version is recoverable. It also says nothing about cost/rate limits (relevant given sibling get_api_usage_stats) or whether team_id scoping changes behavior. For a destructive mutation this is a real gap.

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, zero filler, with the action and the trigger condition front-loaded. It is appropriately sized for the amount of content it chooses to convey, though it is under-specified rather than overwritten.

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?

An output schema exists so return shape need not be explained, but for a destructive 3-parameter mutation with 0% schema coverage the description is missing overwrite semantics, parameter meaning, and scoping behavior. An agent could call it correctly on the happy path but has no basis for judging side effects.

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% across 3 parameters, so the description is the only place meaning could be added — and it isn't. Only 'for a drop' loosely implies drop_id; team_id and channel_preset (which presumably shapes tone/channel of the generated copy) are entirely unexplained, making channel_preset especially opaque.

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 + resource ('Regenerates AI copy pack') and enumerates the artifacts produced (hook, caption, hashtags, CTA). It does not distinguish itself from the sibling 'regenerate_drop_cover', which is a similar regenerate-a-drop-artifact tool, 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?

'Use when the user wants to refresh or improve the social copy' gives an implied trigger condition, but no when-not-to-use guidance and no routing versus update_drop or regenerate_drop_cover. The agent must infer the boundaries from sibling names alone.

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