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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds value beyond them by saying 'No footage is uploaded' (an upload/upload_media distinction the hints don't express) and by previewing that each item carries a deviceId, which partially compensates for the missing output schema.

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?

Three short sentences, front-loaded with the action, then the sequencing rule, then a reassurance. Nothing repeats the title or the annotations verbatim, and every clause carries information.

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 no-parameter, read-only listing with no output schema, the description covers what it returns at a high level and how it fits into the AE tool chain. It doesn't say what to do when the list is empty (e.g., an install/authorize step), which is the main remaining gap for an agent bootstrapping a session.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies there is nothing to supply and instead points at the return shape (connections keyed by deviceId).

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?

States a specific verb and resource ('List your authorized After Effects connections') with a scope qualifier ('authorized'), which cleanly separates it from premiere_list_connections and the other AE tools. An agent can identify what it returns without opening the schema.

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?

'Call this first' gives explicit ordering guidance for the After Effects tool family, and 'each connection carries the deviceId every other After Effects tool needs' explains the dependency that motivates the ordering. It stops short of naming the counterpart (premiere_list_connections) or stating when not to use it.

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