get-results

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention what happens if no script was executed (e.g., returns empty vs. error), whether the operation is idempotent, or if it consumes or clears the results. The description only states the basic action, leaving significant behavioral ambiguity.

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, front-loaded sentence that directly states the tool's purpose. While concise, it could be slightly expanded to include critical context without becoming verbose. The current length is appropriate but borderline too brief.

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?

Given the tool has no output schema, the description should explain the nature of the return value (e.g., text, JSON, file). It also lacks any info on prerequisites (e.g., script must have been run) or side effects. The description is incomplete for a tool that retrieves potentially dynamic data.

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, and the schema coverage is 100% (empty properties). With no parameters, the description is not required to add parameter-level detail; the baseline of 4 applies as the description does not need to compensate for missing parameter information.

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 retrieves results from the last script executed in After Effects. It identifies the resource ('results') and action ('get'), but does not elaborate on what constitutes 'results' (e.g., output text, error logs). This is sufficient to differentiate from siblings like 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?

No guidance on when to use this tool versus alternatives. It does not mention that a script must have been executed previously, nor does it specify that the tool returns empty or errors if no script has run. Sibling tools like run-script are mentioned but not explicitly contrasted.

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