Render a diagram IR to SVG

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

With no annotations, the description carries the full burden and does so well: it discloses the 25,000-byte threshold that switches the result from a text content block to a resource_link fetchable via resources/read, and that invalid IR fails with isError:true rather than emitting broken geometry. Embedding cost and the opt-in default are also made explicit.

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?

Front-loads the core action, then prerequisites, then return-shape and failure semantics in a single dense paragraph with no filler topics. Minor redundancy in the embedFonts justification ('still an added cost worth opting into deliberately') costs it a point.

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?

No output schema exists, so the description properly explains return behavior (inline text vs resource_link and how to fetch it) plus the failure mode. For a 2-param tool with a nested free-form IR object, nothing an agent needs to invoke or interpret the call correctly is missing.

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 already 100%, so baseline is 3. The description goes beyond the schema's field text by framing embedFonts as a deliberate cost tradeoff (subset sized to this diagram's own text, not a fixed cost), which helps the agent decide rather than just describing the flag.

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+resource pipeline: validates an ArchSmith diagram IR and renders it to a complete SVG document. An agent can tell what it produces (an SVG) and from what (an IR) without opening the schema, and the scope is narrowed to ArchSmith diagrams rather than a generic renderer.

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?

Gives a concrete prerequisite flow (call get_schema and get_registry first to learn the IR structure and vocabulary) and conditional guidance for embedFonts (opt in only when portability without installed fonts is required). It does not explicitly state when to prefer this over the sibling validate tool, which is the only gap.

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