render

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'renders to PNG for visual review' without mentioning side effects, output location, permissions, error cases, or any constraints. This is a minimal statement that omits critical behavioral details an agent would need.

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 concise sentence with no redundancy. It front-loads the action and purpose, making it easy to parse quickly.

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 simplicity (one parameter, no output schema), the description covers the basic function but omits details like where the PNG is produced, return format, or any prerequisites. It is minimally complete for a straightforward render operation, but not rich enough to fully guide an agent without additional assumptions.

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 input schema has a single 'path' parameter with 0% description coverage. The description implies 'path' points to an existing .drawio file but does not explicitly define the parameter's format, allowed values, or required structure. It provides marginal implied meaning but fails to adequately compensate for the lack of schema documentation.

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 states a specific verb ('Renderiza'), resource ('.drawio'), and output (PNG) with a clear purpose (visual review). It implicitly distinguishes itself from sibling tools that focus on searching, building, or linting, making its role unambiguous.

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 purpose is clear enough to infer when to use it (when you want to visually inspect an existing drawio file), but it does not explicitly mention when not to use it or point to alternative tools. Since the context is self-evident and the sibling list provides indirect alternatives, a 4 is appropriate.

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