Render a preview frame

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

With no annotations, the description does useful work by disclosing that output goes to a new .mcp-artifacts file, that existing files are never overwritten, and that a built tcomposer binary is required. It does not say what happens if outputPath already exists, what is returned, or how timeoutMs/shrink/threads affect behavior, so the burden is only partly met.

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?

Three short sentences with zero filler; the action, the safety guarantee, and the prerequisite all appear up front. Nothing in the text is redundant with the title or with itself.

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 six-parameter tool with no annotations and no output schema, the description covers purpose and safety but leaves parameter meaning and return values entirely unaddressed. An agent could call it, but not confidently configure frame, shrink, threads, or timeout.

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?

Schema description coverage is 0% across six parameters, and the description explains none of them — frame, shrink, threads, timeoutMs, and outputPath are all left for the agent to guess. The only hint is that output lands in a 'new' file, which loosely implies outputPath is never overwritten.

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 and resource: render a single scene frame with tcomposer, writing to a new .mcp-artifacts file. The 'one scene frame' scope distinguishes it in spirit from render_scene, but it never names that sibling, so an agent must infer the split.

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?

Usage is only implied by 'Render one scene frame' and the stated prerequisite of a built tcomposer executable. There is no explicit when-to-use/when-not, and the obvious alternative render_scene is never mentioned or contrasted.

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