create_interactive_session

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

Annotations are minimal (readOnlyHint false, etc.), so description carries the burden. It says 'create' implying stateful resource creation, but lacks details on side effects, resource limits, or cleanup. No contradiction, but could be more informative.

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. Efficient but perhaps too brief for a tool with multiple optional parameters and significant context.

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?

With 4 parameters, an output schema, and siblings, the description is too sparse. It does not explain what a session is, how to start it, or what the expected outcome is. Lacks completeness.

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 4 params with no descriptions (0% schema coverage). The description does not explain any parameter meaning, leaving the agent without guidance on how to use session_id, command, env, or cwd.

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 'Create a new interactive OpenROAD session' clearly states the action (create) and resource (interactive OpenROAD session), distinguishing it from siblings like 'inspect_interactive_session' and 'terminate_interactive_session'.

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 alternatives like 'interactive_openroad_exec'. There is no mention of prerequisites, exclusions, or context for using this tool over others.

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