prompt_director_inspect

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

Clearly declares it's read-only ('never changes the workflow'), explains redaction of secrets and tensors. With no annotations, the description fully informs about behavior and safety.

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?

Five sentences, well-structured, front-loaded with main purpose, and no unnecessary information. Every sentence adds value.

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?

Complete for a low-complexity tool: covers input, output specifics, usage context, and behavior. No missing information given the lack of output schema or nested objects.

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?

Only one parameter (node_id) with 100% schema coverage. Description adds meaningful context: 'Optional... omit to list all recent...'. This goes beyond the schema's description by explaining default behavior.

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 reads the runtime state after Prompt Director nodes execute, lists what it returns (node id, kind, context, etc.), and differentiates it from graph inspection tools. It uses specific verbs and resource.

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?

Explicitly says when to use (with live panel graph audit) and what it offers versus alternatives. Also explains how to use the optional node_id parameter, providing clear usage context.

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