ae_render_comp

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

Discloses blocking behavior and return of output path, but with no annotations, more context is needed: prerequisites, side effects, error handling, authorization.

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, zero wasted words, front-loaded with purpose.

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?

No output schema, and description only minimally explains return value. Ignores error scenarios, prerequisites, and blocking implications. Incomplete for a rendering 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?

Schema covers 75% of parameters with descriptions, but the comp parameter lacks description both in schema and tool description. No additional meaning added beyond schema.

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?

Clearly states it renders a composition to a video file via the Render Queue. Verb 'render' and resource 'composition' are specific, and it distinguishes from sibling tools like ae_render_frame.

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?

Implies usage for rendering video files, but no explicit when-to-use or alternatives. Mentions blocking nature, which is useful but insufficient for distinguishing from siblings.

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