Render Infographic

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

With no annotations, the description must disclose behavior. It alerts users that the DSL is space-separated key-value (NOT YAML), which is a critical pitfall, and states the output is a PNG. However, it omits error handling, invalid-syntax behavior, and other potential constraints, leaving some transparency gaps.

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 longer than average but justified by the complexity of the DSL. The code block and template list are necessary for correct usage. Each sentence contributes value, though the content could be slightly trimmed without losing essential information.

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 tool uses a complex DSL, so the example and template disclosure are essential. It states the return type (PNG) and provides template examples, but does not cover output dimensions (though schema parameters define this) or error behavior. Overall, it is largely complete for the tool's complexity.

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?

All parameters have schema descriptions (100% coverage), giving a baseline of 3. The description significantly enriches the 'syntax' parameter by providing a complete DSL example and template list, adding meaning beyond the schema's one-line description. Other parameters remain adequately covered by the schema.

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 'Render an infographic from DSL syntax and return as PNG image', specifying both the operation (render) and the resource (infographic from DSL syntax), along with the output format. This is a precise, verb+resource statement that fully distinguishes the tool's purpose.

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 provides a detailed DSL syntax example and a template list, giving clear context on how to construct input. It doesn't mention alternatives since none are listed as siblings, but it does not explicitly state when to use the tool instead of others. The context is clear and actionable.

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