ae_set_layer_3d

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

No annotations are provided, so the description carries full burden. It says 'Toggle' but does not clarify if the function flips the state or sets it absolutely. The 'enabled' parameter defaults to true, but the description is silent on this behavior. Some ambiguity remains.

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 description is a single sentence that is concise and front-loaded with the action. Every word serves a purpose with no redundancy.

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?

Given 4 parameters and no output schema, the description is mostly adequate but lacks explanation for the 'comp' and 'enabled' parameters. It does not describe what happens when 'enabled' is omitted (defaults to true). For a simple tool, it covers the core action but leaves gaps.

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 50%; the schema describes 'layer' and 'allLayers' but not 'comp' or 'enabled'. The tool description adds minimal information beyond the schema: it explains that allLayers applies to every layer, but does not cover comp or enabled. The meaning of 'enabled' (default true) is not explained, so parameter semantics are insufficient.

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 clearly states the verb 'Toggle', the resource 'layer's 3D switch', and the scope 'every layer in the comp'. This distinguishes it from sibling tools like ae_set_blend_mode or ae_add_camera, which have different purposes.

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 explicitly says 'Required before a camera move affects 2D layers', giving a clear when-to-use hint. However, it does not mention when not to use or alternatives, which is acceptable for a straightforward toggle operation.

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