ae_list_presets

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

No annotations are provided, so the description carries the burden; it does disclose read-only behavior ('Changes nothing') and the query matching rule (all words must match the path). It omits recursion behavior, case sensitivity, and what happens when no roots are given beyond the default.

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?

Three short sentences, front-loaded with the action and scope, then query semantics, then the read-only reassurance. Nothing redundant.

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 3-parameter read-only lookup with no output schema and no annotations, the description covers purpose, scope, and query matching adequately. Minor gap: results/pagination behavior given the max default is left implicit.

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 67%: 'roots' and 'max' are documented in the schema, but 'query' has no schema description. The description compensates by defining query semantics ('Words in query must all match the preset path, e.g. blur in'), adding real meaning beyond the 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?

Specific verb+resource: 'Find animation presets (.ffx)' with the search scope ('standard Adobe preset folders or given folders'). It is clearly distinguishable from siblings like ae_list_available_effects and ae_apply_preset.

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?

'Changes nothing' implies a safe lookup and the description implies use for locating presets, but it never says when to use this versus ae_list_available_effects or the follow-up ae_apply_preset. Usage is inferable but not stated.

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