render_math

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions the output format (PNG data URI) but fails to disclose limitations like supported LaTeX packages, rendering errors, or performance characteristics. For a rendering tool, more detail is needed.

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 a single sentence, concise and front-loaded. It wastes no words, but improvements could include a slightly more structured listing of key points (e.g., output format, parameter hints).

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 output schema exists (not shown), the description can skip return value details. However, it fails to provide context for the three parameters (which have no schema descriptions) and does not differentiate this tool from similar rendering tools or explain proper LaTeX input format. The description is insufficient for correct 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?

The schema has 0% description coverage for parameters, and the description provides no additional meaning. It does not explain that 'latex' should be a valid LaTeX expression, nor the effect of 'fontsize' and 'dpi' beyond their names. This severely limits the agent's ability to use the tool correctly.

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 action ('Render'), the resource ('arbitrary LaTeX math'), and the output ('to a PNG data URI'). It is specific and distinguishes itself from sibling tools which perform symbolic math, plotting, or other operations.

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 implies usage when a rendered LaTeX image is needed, but it does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions or prerequisites. Given the many math-related siblings, some guidance would be beneficial.

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