list-installations

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

The verb 'Discover' suggests a read-only operation with no side effects. There are no annotations to contradict this, and the description does not mention any modifications or destructive actions. A slightly higher score would require an explicit statement of non-mutating behavior.

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, concise sentence that captures the essence without fluff. It is front-loaded with the main action and result, making it easy to parse quickly.

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?

The description does not specify the return format or structure (e.g., a list of objects with version and path fields). Since there is no output schema, this missing detail could lead to ambiguity. However, for a simple discovery tool, the lack of return details is partially compensated by the clarity of the purpose.

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?

The tool has zero parameters, so the baseline score of 4 applies. There is no parameter documentation needed, and the description does not imply any hidden inputs.

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's function: discovering installed After Effects 2024+ versions and aerender paths. It uses a specific verb ('Discover') and names the resource, distinguishing it from other tools like get-request or render-composition.

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 implies when to use it (when needing to know installed versions/paths) but does not explicitly contrast it with alternatives or state conditions for selection. The purpose is obvious, but explicit guidance is absent.

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