Read a property

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

Annotations declare readOnlyHint=true and openWorldHint=false. The description adds that it reads current value, keyframes, expression, and children, which goes beyond the annotations and explains the multi-part return behavior. It does not contradict annotations.

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 primary function and return content. The second sentence adds a practical hint about discovering parameter names, earning its place.

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?

For a read tool with annotations covering safety and no output schema, the description is mostly complete. It explains the return includes value, keyframes, expression, and children. It could mention that 'comp' and 'layer' are optional and default to active/selection, but the schema already covers that; nothing critical is missing for calling it correctly.

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 100%, so the schema already documents all four parameters. The description adds value by showing that 'property' can be an array for exact addressing and notes that children listing reveals parameter names, but it doesn't go deep into time/format semantics. Given full schema coverage, a 4 is appropriate.

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?

States a specific verb ('Read') and resource ('a property'), and explicitly mentions what is returned: current value, keyframes, expressions, and children. This distinguishes it from sibling tools like ae_set_property, ae_set_keyframes, and ae_set_expression.

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 says it also lists property children, which is how you discover exact parameter names, giving a clear use case for exploration. It doesn't explicitly say when not to use it versus alternatives, but as a read tool it is clearly distinct from the set/remove/apply siblings.

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