Visualize Cluster Topology

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

No annotations are provided, so the description must fully disclose behavioral traits. It states a diagram is generated, but does not mention read-only nature, required permissions, output format, or performance impact. Lacks sufficient transparency for a cluster-scoped tool.

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?

Single sentence, no fluff. Front-loaded with the action and scope. Every word is meaningful.

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 no parameters, annotations, or output schema, the description is minimal. It explains the diagram's content (nodes, namespaces, pod distribution) but lacks details on diagram style, level of detail, or what 'high-level' means. Adequate but could be more informative.

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?

There are no parameters, so the schema is fully covered (100%). The description adds no parameter-specific meaning, but the absence of parameters means no additional documentation is needed. Baseline score of 4 is appropriate.

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 it generates a Mermaid diagram of cluster topology covering nodes, namespaces, and pod distribution. It is specific about the resource and action, but doesn't explicitly differentiate from sibling tools like 'render_cluster_topology' or 'visualize_namespace'.

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 on when to use this tool versus the many similar visualization tools (e.g., render_cluster_topology, visualize_namespace). The description does not mention alternatives, prerequisites, or context.

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