After Effects status

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description focuses on what annotations can't say: it lists every running instance, explains how the session's target is selected, and describes failure behavior (the error states why, e.g. not running or not accepting scripts). Only return formatting/pagination-like detail is absent, which is minor here.

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?

Four short sentences, each doing distinct work: what it reports, multi-instance handling, when to call it, and where to go instead. The most decision-relevant facts (what it returns, call-first advice) are front-loaded.

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?

With a single optional parameter, no output schema, and annotations covering safety, the description still enumerates the returned fields and explains error behavior and sibling routing. There is no meaningful gap an agent would need filled before calling it.

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 coverage is 100%, so baseline is 3; the description goes beyond the schema by explaining the scenario in which `instance` matters (multiple AE instances open) and that omitting it retains the current target. That situational framing is genuinely additive rather than a restatement.

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+resource ('check the connection to After Effects') followed by an enumeration of exactly what is reported: version, OS, open project, active item, permission mode, busy state. It explicitly distinguishes itself from ae_get_project_info, which covers a different surface (project contents).

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?

Gives a clear entry condition ('Call this first if unsure AE is reachable') and names the alternative for a related need ('For the project's contents use ae_get_project_info'). The multi-instance case is also routed explicitly: pass `instance` to choose the target when several are open.

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