list-available-effects

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

With no annotations provided, the description must carry the behavioral burden. 'List' implies a read-only operation, which is accurate, but the description does not disclose potential performance implications of listing all effects, the default maxResults, or the return format. It adds the optional text filter behavior, but overall transparency is minimal yet not misleading.

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 a single sentence that is front-loaded with the verb and resource. It is concise, contains no fluff, and effectively communicates the core purpose.

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 simple list tool with no output schema, the description provides the basic operation but lacks details about the return value structure (e.g., whether it returns names, objects with matchName and category). Since there is no output schema, the description should clarify what is returned, making this a notable gap.

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 parameters are already well-documented. The description's mention of 'optional text filter' aligns with the query parameter but adds no additional semantics beyond the schema. Baseline of 3 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?

The description clearly states the tool lists all effects available in the After Effects installation, using the specific verb 'List' and identifying the resource with scope. It also distinguishes itself from sibling tools like list-layer-effects (which lists effects on a layer) and list-presets (which lists presets) by specifying 'available in this After Effects installation.'

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 provides no guidance on when to use this tool versus alternatives such as list-layer-effects or search-presets. There is no explicit 'when to use' or 'when not to use' context, so the agent is left to infer usage solely from the name and purpose.

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