List scripts

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond annotations: the exact folders searched, the fact that AE must be running, and what fields each script entry includes. It does not discuss ordering or pagination, but that is a minor omission for a local read-only listing.

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 compact and front-loaded: it first defines the list scope, then what each result contains, then the prerequisite, then the alternatives. Every sentence adds actionable 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?

For a read-only listing tool with no output schema, the description explains search locations, returned fields, the AE-running prerequisite, and how to proceed after listing. There are no significant gaps for correct invocation.

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 description coverage is 100%, so the single optional nameContains parameter is already fully documented in the schema. The description does not add filtering semantics beyond the schema, which is acceptable at the baseline when schema coverage is complete.

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 states a specific verb and resource: list the user's own After Effects scripts, including the concrete search locations (AE Scripts folder, ScriptUI Panels, and configured scriptFolders). It also names the returned fields and distinguishes this discovery tool from ae_run_script_file and ae_run_script.

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?

It clearly says to use this tool to find scripts, then explicitly routes execution to ae_run_script_file and routes self-written code to ae_run_script. It also gives the prerequisite that After Effects must be running.

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