project_render

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

Without annotations, the description carries full burden. It discloses blocking behavior and use of render dialog automation, but does not explain side effects (e.g., file overwriting, project state changes), cancellation, or return value. Some transparency, but notable gaps.

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 that efficiently conveys the core purpose and a key behavioral trait (blocking). Every word adds value, no unnecessary content.

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 tool with three parameters and no output schema, the description is too minimal. Missing details on parameter meaning, error handling, return behavior, and interaction with project state reduce its utility for correct tool selection and invocation.

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% and the description adds no detail about parameters. It does not explain the purpose or constraints of 'path', 'format', or 'mode', leaving the agent without necessary guidance for correct invocation.

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?

Description clearly states the action ('Trigger render to disk') and resource (the project). It distinguishes this tool from sibling tools by specifying it uses FL's render dialog automation and blocks until complete, which is unique among the listed tools.

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 context ('blocks until complete') but does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. The blocking behavior is useful, but lacking explicit guidance.

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