visualize_process_tree

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

No annotations are provided, so the description carries full burden. It states output formats (PNG+SVG) but does not disclose side effects, error handling, or whether it's read-only. The behavior is partially transparent but lacks detail on what 'render' entails (e.g., returns files, displays, etc.).

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, perfectly concise sentence that front-loads the action and output. No superfluous words. It earns its place by being direct and informative without redundancy.

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 low complexity (1 param, no output schema, no annotations), the description covers the basic purpose but lacks details on the output (e.g., are PNG and SVG files returned as URLs or base64?), error handling, and prerequisites. It is sufficient for a simple tool but not fully complete.

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?

Schema has one required parameter 'tree_id' with 0% description coverage. The only hint in the description is 'from discover_process_tree', which implies the origin of the ID but does not explain its format, constraints, or how to obtain it. The schema itself offers no additional details.

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 ('process tree'), and the outputs ('PNG + SVG'). It references the source tool 'discover_process_tree', distinguishing it from sibling visualization tools.

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 after discovering a process tree. While it doesn't explicitly say when not to use or list alternatives, the context of sibling tools provides clarity. No explicit prerequisites are mentioned, but the single parameter 'tree_id' hints at the need for a prior discovery result.

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