Read the last result After Effects wrote when a slow command times out, so you can inspect the completed output.
Read the last result After Effects wrote. Only needed if a command timed out because it was slow (e.g. heavy effects).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0-ibintec.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses a behavioral trait — that results are only worth fetching after a slow/timed-out command — but omits what happens if no result exists, the return format, and any read-only/error 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?
Two short sentences, zero filler, with the core action front-loaded and the gating condition immediately after. Every sentence earns its place.
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 zero-parameter retrieval tool with no annotations or output schema, the description covers purpose, trigger condition, and source of the data. It could say a bit more about the shape/contents of the returned result, since no output schema exists to carry that.
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 takes zero parameters, so there is nothing for the description to clarify beyond the schema. The baseline of 4 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?
States a specific verb ("Read") and resource ("the last result After Effects wrote"), which is clearly distinct from the action-oriented siblings like run-script and apply-effect. It doesn't explicitly name a sibling to differentiate against, but the retrieval-vs-action distinction is self-evident here.
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?
Gives a concrete when-to-use condition ("Only needed if a command timed out because it was slow") plus an example (heavy effects), which effectively also states when-not to use it. It does not name a specific alternative tool to check first, so it falls short of a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.