Refresh asset previews

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which align with the description's 'Capture' verb. However, the description adds no extra behavioral context such as file overwrite behavior, success/failure conditions, or performance impact. The minimal disclosure leaves the agent guessing about side effects.

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 with no unnecessary words, but it is too terse to be fully effective. It lacks structure such as bullet points or usage examples that would improve clarity without adding significant bulk.

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?

Despite a low-complexity tool with 3 parameters and no output schema, the description omits critical details: what happens on success (e.g., file saved at given path), return behavior, error cases, and limitations. The agent cannot infer usage fully.

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 input schema has 0% description coverage for parameters, and the tool description does not explain the purpose or constraints of 'node_path', 'file_path', 'width', or 'height'. The agent receives no semantic help beyond raw JSON structure.

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 captures preview PNG assets from one or more TOP nodes, which is specific and distinguishes from siblings like 'record_movie' or 'render_output' that focus on different outputs. However, it does not explicitly differentiate from 'capture_to_vault' which also captures previews.

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 like 'render_output' or 'capture_to_vault'. There is no mention of prerequisites, scenarios, or exclusion criteria.

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