get_render_result

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 clearly explains the async nature, the return of a result dict upon completion, a 'still running' status, and the polling behavior with exponential backoff. It does not mention authentication or side effects, but for a polling tool the described behavior is thorough and transparent.

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 well-structured and appropriately sized. It covers the core purpose, return behavior, polling strategy, and a usage note, with every sentence contributing value. The exponential backoff details and the IMPORTANT directive are useful and not redundant, achieving high information density without being verbose.

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's async complexity and the existence of an output schema, the description is largely complete: it explains polling, statuses, backoff, and a reset condition. However, it does not mention the sibling 'get_render_status', which could clarify when to use this tool versus that one, leaving a minor 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?

Schema coverage is 100%, so the baseline is 3. The description adds minimal meaning beyond the schema—it mentions that render_id comes from render_scene(), but the schema already says 'The render_id returned by render_scene().' Thus the description does not significantly enhance parameter understanding beyond the structured definition.

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 a specific verb and resource: 'Poll for the result of an async render started by render_scene()'. It is unambiguous about what the tool does, but it does not explicitly distinguish itself from the sibling tool 'get_render_status', leaving some potential confusion about when to use which.

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 explicit usage guidance: keep polling until status is 'completed' or 'failed', use exponential backoff (1s, 2s, 4s, 8s, cap at 30s), and reset the count on completion/failure. It also includes a strong directive to always use this MCP tool instead of writing standalone manim scripts, clearly stating when to use this tool versus an alternative approach.

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