render_glyph

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

Annotations are all false, so the description must carry behavioral transparency. It mentions 'Persist' implying a side effect, but does not explain what persists or whether it modifies state. It lacks details on side effects, idempotency, or error behavior.

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 brief and front-loaded with the primary action. It avoids excessive detail, though the word 'Persist' adds mild ambiguity without much benefit.

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 eight parameters and no schema descriptions, the description leaves too much unspecified. It does not mention output format specifics, parameter constraints, or any context about revisions and comparison, making it incomplete for reliable 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 coverage is 0% and the description only vaguely references 'UFO revision', 'guides/handles', and 'comparison'. It fails to map parameters like width, height, guides, points, revision, and compare_revision to their meanings or relationships.

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 clearly identifies the resource (glyph) and the action (render and return PNG content), and it distinguishes from text rendering by referencing a 'UFO revision'. The phrase 'Persist and return' is somewhat ambiguous about whether it saves or simply produces, but the core purpose is clear.

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 no explicit guidance on when to use this tool versus alternatives like render_text or glyph_get. It mentions 'Comparison uses the same frame' which hints at compare_revision, but does not clarify scenarios or exclusions.

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