project_render

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

Discloses two valuable behavioral traits: it uses FL's render dialog automation and blocks until completion. However, with no annotations, it is silent on side effects like overwriting existing files, error/failure behavior, and whether the call requires UI focus or can run headless—gaps for a write-producing operation.

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 compact and front-loaded with the action, then adds essential behavioral context in a parenthetical. Every word contributes value with no fluff.

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?

With 3 parameters, 1 required, no annotations, and no output schema, the description is too thin: it doesn't explain return values, error behavior, parameter semantics, or output-side effects. It covers the blocking nature but leaves an agent guessing about path format and how to interpret the result.

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?

With 0% schema description coverage, the description needed to clarify that 'path' is the output file path and explain the mode/format interplay. It says nothing about any parameter. The enums are self-explanatory, but the required 'path' remains ambiguous (output file vs. project file vs. directory), and the description does not compensate for the schema's silence.

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 ('Trigger render') and resource ('disk'), which is distinct from project save/load siblings. The parenthetical about FL's render dialog automation further clarifies the mechanism. No ambiguity about what operation this invokes.

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 clearly positions this tool as the one to use when rendering/exporting to disk, distinguishing it from save or playback tools. It does not explicitly state when not to use it or list prerequisites, but the context is clear enough for selection among siblings.

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