ae_scene_info

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

Despite no annotations, the description clearly states what the tool returns (list of compositions with properties) and implies it is non-destructive ('inspect'). It does not explicitly confirm no side effects, but the behavior is well-specified for a read operation.

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: first details output, second provides usage advice. No wasted words, front-loaded with the most important 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?

Given no output schema, the description details the output structure (size, frame rate, duration, motion-blur, layers with parents). It fully specifies what the agent will get from this tool.

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 has no parameters, and the description explains the tool's output comprehensively. With 0 parameters, the baseline is 4, and the description adds context about what will be retrieved.

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 uses the verb 'inspect' to clearly state the tool's purpose: listing compositions with detailed attributes (size, frame rate, duration, etc.). It distinguishes from sibling tools that are for creation or modification, making it clear this is a read-only discovery tool.

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?

The description explicitly advises 'Use this first to see what exists,' which is a strong usage guideline. It doesn't exclude use cases, but the context implies it's for initial inspection, earning a 4.

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