papercanvas_render

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses that the operation is strictly read-only on the IR, that output files are written next to the IR, and that outputs are true vector and editable. It does not say whether existing files are overwritten, what permissions are needed, or how errors are surfaced.

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?

Two tightly written sentences, front-loaded with the action and formats. Every clause adds information: the format list, the output location, the vector/editability guarantee, and the read-only constraint.

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 two-parameter render tool with no output schema and no annotations, the description covers the core action, output location, and read-only nature. It is incomplete on the meaning of the required path parameter, overwrite behavior, and what is returned or reported to the caller.

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%, so the description must compensate for both parameters. It clarifies the formats parameter with a concrete list example, but the required path parameter is never explained beyond the indirect hint that outputs are written next to the IR.

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 states a specific verb and resource: render the figure to svg/pdf/pptx. It is distinguishable from siblings like papercanvas_create or papercanvas_patch, but it does not explicitly contrast itself with them or clarify that those siblings manipulate the IR rather than export it.

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 implied: use this when you need output files in svg, pdf, or pptx. However, there is no explicit when-to-use versus when-not-to-use guidance, no mention of prerequisites, and no routing to alternatives among the sibling tools.

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