ae_purgeMemory

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description usefully discloses that undo history and image caches are among the things purged, which the annotations do not convey. It stops short of saying whether the purge is reversible or what state the project is left in, but it adds real context beyond the structured hints.

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?

A single front-loaded sentence pairing the action with its scope and its rationale; nothing is padded or repeated.

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 one-parameter cache utility with annotations covering the safety profile and no output schema, this is nearly sufficient. The residual gaps are the undocumented 'snapshot' target and the default when no target is supplied.

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%, so the description must carry the parameter load; it names 'all memory & disk cache', 'undo', and 'image cache', which map onto three of the four enum values but silently omits 'snapshot'. It also never states the behavior when target is omitted, despite the parameter being optional.

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 (purge) and resource (After Effects caches), enumerating the cache types affected and the intended benefit (free RAM on heavy projects). No sibling tool in the list performs anything similar, so an agent can route to it unambiguously.

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?

'to free RAM on heavy projects' gives an implicit trigger condition, but there is no explicit when-not guidance, no mention of prerequisites (project must be open, whether it can be run mid-render), and no alternatives to consider. Usage must be inferred from the motivation clause alone.

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