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

With no annotations, the description carries full behavioral burden; it does add useful traits (version keep/discard/revert semantics, normalized overlay geometry, voice/emotion/gender narration options, language-dependent extras). However, it never distinguishes read actions from mutations, says nothing about async job behavior (a likely trait given the adgpt_job sibling), reversibility of deletes, or auth requirements.

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 purpose statement is front-loaded, but roughly half the text is a verbatim re-listing of the 30-value enum already present in the schema, which earns little. The grouping into plain image/video vs inAction families is the only added value from that enumeration.

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 30-action dispatcher with no annotations, no output schema, and a passthrough params object, the definition gives a reasonable map plus a discovery mechanism. It still leaves the agent without per-action effect, output, or async expectations, so it is adequate but clearly short of complete.

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 is a passthrough (action enum + free-form params object) at 50% coverage, so the description should compensate. It does the next-best thing by telling the agent to call adgpt_capabilities with the operationId for per-action parameters, but it explains no parameter semantics itself, so it is only partially compensating.

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?

Opens with a specific verb/resource pair ("Post-generation editing of image and video assets") and enumerates the concrete capability families (prompt edits, overlays, narration re-dub, version control, share links). It is distinguishable from resize/single-asset siblings, though the 30-action dump blurs the core purpose more than it clarifies.

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?

It implicitly scopes in-action editing ("inAction* works on completed UGC in-action ads"), which hints at the boundary with adgpt_in_action, but never states when to pick this tool over adgpt_single_asset, adgpt_image_resize, or adgpt_ugc. The only explicit guidance is a discovery pointer, not a selection rule.

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