ae_guidelines

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

No annotations are provided, so the description carries the full burden, and it does disclose a real behavioral trait: 'Does not contact After Effects' tells the agent this is a side-effect-free local read that presumably works without a live AE connection. It stops short of describing return size/format or any bridge prerequisites, but for a static doc fetch this is solid disclosure.

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, front-loaded with the verb and resource. The parenthetical topic list is dense but earns its place by letting the agent judge relevance without invoking the tool.

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?

There is no output schema and no parameters, so the description must stand alone, and it adequately covers what the tool returns (full guidelines) and when to call it. A note on output length/format would make it complete, but nothing an agent needs in order to call it correctly is absent.

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 and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level detail is required or missing.

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: 'Read the full motion-design and workflow guidelines for this bridge', with a parenthetical inventory of the covered topics (easing, bounce, text animators, stagger, track mattes, motion blur, review loop, ExtendScript pitfalls). This clearly separates it from every sibling, which are all stateful After Effects operations rather than documentation reads.

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 it once before designing or animating' gives explicit timing and cardinality (once), which is exactly the routing decision an agent needs. The closing clause also signals it is not a substitute for the actual AE action tools.

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