Add solid layer

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

The description indicates a write operation ('Add'), consistent with readOnlyHint=false. However, it fails to disclose behavioral traits such as whether the composition must exist, whether the operation modifies the current project, or any side effects. With annotations providing minimal info, the description carries insufficient burden.

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 concise with two efficient sentences, no redundancy, and front-loaded purpose. However, given the tool's complexity (10 parameters), it is arguably too brief to cover essential 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?

With 10 parameters, no output schema, and minimal annotations, the description is incomplete. It does not explain what the tool returns, how composition is identified, or the meaning of defaults. The agent lacks sufficient context to use the tool correctly without external knowledge.

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 coverage is 0%, and the description adds no parameter-specific information beyond noting defaults. It does not explain color format, position structure, or the role of composition_id versus composition_name. The description fails to compensate for the lack of schema documentation.

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 tool adds a solid layer to a composition, with defaults for dimensions, duration, and position. This distinguishes it from sibling tools like after_effects_add_text implicitly, but could be more explicit about what a 'solid layer' entails.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., after_effects_add_text, after_effects_import_file). There is no mention of prerequisites or context for when adding a solid layer is appropriate.

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