render_text

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

The description does not disclose side effects, permissions, authentication requirements, or potential limitations. Annotations indicate readOnlyHint false but provide no additional context, leaving behavioral impact unclear.

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 extremely concise, consisting of two sentences with no redundant or extraneous content. It efficiently communicates the primary action and an optional feature.

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?

Given the tool's complexity (8 parameters, output schema, optional comparison logic), the description is far too minimal. It omits critical details about parameter semantics, output format, revision handling, and error behavior (e.g., 'missing Unicode is reported'). The description does not adequately prepare an agent to use the tool correctly.

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?

The schema has 8 parameters with zero description coverage. The text vaguely references 'revision' and 'compare_revision' but does not explain the meaning or expected values of parameters like width, dark, kern, sizes, or project_id. No parameter-level detail is provided.

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 states the tool compiles a revision, shapes with HarfBuzz, and returns monochrome FreeType PNGs, also mentioning an optional comparison feature. It is specific enough to understand the core function, though it does not explicitly differentiate from sibling tools such as render_glyph.

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?

No guidance is provided on when to use this tool versus alternatives like render_glyph or font_build. The mention of 'optional same-conditions revision comparison' describes a feature, not a usage context or decision criterion.

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