nox_run_session

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

No annotations provided, so description carries full burden. It describes basic behavior (running nox sessions) and return values, but lacks details on destructive actions, auth needs, or error conditions beyond exit codes.

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?

Description is well-structured with intro, args, returns, and example. Front-loaded purpose, every sentence adds value. No redundant text.

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?

Covers usage, parameters, return values, and example. Output schema exists. Minor gaps: doesn't specify error handling for invalid sessions or timeouts, but adequate for a command-executing tool.

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 description coverage is 0%, but description provides thorough parameter documentation: constraints on sessions (alphanumeric, hyphens, underscores), tags (list), keywords (expression), python version, timeout default. Adds significant meaning beyond schema.

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 verb 'Run' and resource 'nox sessions', specifying execution of one or more sessions. It distinguishes from sibling tool nox_list_sessions by advising to list sessions first.

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 advises to use nox_list_sessions first to discover sessions, providing clear context. It mentions filtering options but does not explicitly state when not to use this tool.

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