runCollection

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

The description adds that the tool returns detailed test results and execution statistics, and notes advanced parameters are unavailable. Annotations already indicate idempotent and non-destructive behavior, so the description provides moderate additional context.

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 two sentences and a note, front-loading the core purpose and output, with no superfluous words.

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?

Despite clear purpose and well-documented parameters, the description lacks detail on the structure of the returned test results and statistics. With no output schema, the agent cannot fully understand what the tool returns, which is insufficient for a 9-parameter 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?

All parameters are documented in the schema with 100% coverage. The description adds that the environment parameter supports variable substitution and notes the absence of advanced runtime options, which provides some extra meaning but does not significantly enhance parameter understanding.

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 runs a Postman collection by ID and provides detailed test results and statistics, distinguishing it from sibling tools used for creation or retrieval.

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 (run a collection) but does not explicitly state when to use this tool versus alternatives, nor does it provide prerequisites or exclusions.

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