render_diagram

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states it renders, without mentioning side effects, auth requirements, rate limits, or whether it is read-only. For a complex tool like this, more transparency on behavior 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 two sentences long with no unnecessary words. It front-loads the purpose and then states the constraint. Every sentence is essential.

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 complexity of the tool (multiple diagram types, many options), the description is too minimal. It does not mention supported diagram types, output formats, or any constraints beyond schema conformance. The schema itself is huge, but the description should provide a high-level overview to help the agent decide quickly.

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 single parameter 'diagram' is a complex object with extensive documentation in the input schema itself. The tool description adds value by referencing the 'DiagramInput schema', implying the agent must consult it. Since the schema already contains detailed descriptions for sub-properties, the description's semantic contribution is minimal but sufficient.

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 renders a declarative JSON diagram into a visual representation, with a specific resource (diagram JSON) and action (render). It also mentions the input must conform to a schema, which distinguishes it from the sibling tool 'get_schema' that likely retrieves the schema.

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. The only sibling is 'get_schema', which serves a different purpose, but the description does not specify when to choose rendering over anything else. Lacks when-to-use or when-not-to information.

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