get-results

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool gets results, which implies a read-only operation, but it does not disclose what happens if no script has been run, whether results are cleared after retrieval, or any error conditions. The description adds minimal behavioral context beyond the action itself.

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, straight-to-the-point sentence that wastes no words. The key action and object are front-loaded, making it instantly clear and appropriately concise.

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 zero-parameter getter, the description covers the primary purpose, but it lacks an explicit mention of the return value's structure or format. Since there is no output schema, the agent only knows it will receive 'results' without any indication of shape, which is a notable gap in completeness.

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 schema provides full coverage by definition. Since there are no parameters to document, the description is not required to add parameter-level semantics, and the baseline of 4 for zero-parameter tools applies.

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 verb 'Get' clearly identifies this as a retrieval operation, and the resource is specifically 'results from the last script executed in After Effects', which distinguishes it from sibling tools like run-script or setLayerExpression. The scope is precise and unambiguous.

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 that this tool should be used after running a script by referencing 'the last script executed', but it does not explicitly mention run-script as a prerequisite or state when not to use this tool. No alternatives are named, so the usage context is only implied rather than explicitly guided.

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