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

Beyond readOnlyHint=false, it discloses that Picorn resolves all placeholders internally and that the tool 'Returns an inline preview and public creationUrl,' which matters since there is no output schema. It also draws a behavioral boundary around not performing the conversion in a separate admin call.

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?

Six sentences cover purpose, mechanism, three engine options, constraints, and return value with no filler, and the purpose is front-loaded. The engine-enumeration sentence is dense, but each clause carries distinct information that earns its place.

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?

The mechanism, engine options, and return shape are covered, which is substantial for a tool with no output schema and zero param descriptions. However, width, height, and preview parameters are entirely undocumented, and there is no failure behavior or worked example to anchor the declarative workflow.

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 schema description coverage at 0%, the description carries full burden. It richly specifies the svg parameter (placeholder <rect> elements, data-clipart-engine/prompt/num-colors/keep-bg attributes) but says nothing about width, height, or preview beyond schema min/max constraints.

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 first clause, 'Render your SVG through Picorn with real typography and declarative image workers,' states a specific verb (render) and resource (SVG). The placeholder mechanism and engine-mode detail make it unmistakably distinct from siblings like picorn_generate_image or picorn_editor_render_project.

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 gives conditional backend-selection guidance (svg-converter for fresh ComfyUI scenes, z-image-turbo for raster cutouts, library for existing vectors) and an explicit when-not instruction: 'never call the admin converter or return generated base64 yourself.' It does not name sibling tools as alternatives, but the internal routing conditions are explicit.

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