Run a collection

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

Annotations declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered, yet the description never acknowledges that executing a collection fires real requests against external systems. It does add useful context the annotations do not: what the run returns (test results, execution statistics) and which runtime knobs are unsupported.

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?

Three tight sentences that front-load the core action and its output before the environment note and limitation. Every sentence carries information, with only minor redundancy between 'detailed test results' and 'execution statistics'.

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 no output schema, the description correctly steps in to describe the return payload, and it flags a capability gap. However, for a tool annotated destructive and open-world, it omits permission requirements and the side effects of actually executing collection requests, leaving an important behavioral hole.

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 100% across all 9 parameters, so the schema already documents collectionId, environmentId, timeouts, and the stop/abort flags with defaults. The description only reinforces environmentId and notes missing delay options, adding little beyond the structured fields; baseline 3 applies.

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?

States a specific verb (Runs) and resource (Postman collection) plus the identity input (by ID) and what it produces (test results and execution statistics). It is clearly distinguishable from read-only siblings like getCollection and from generateCollection, though it never names an alternative to route against.

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?

There is no guidance on when to choose this over siblings such as getCollection, generateCollection, or duplicateCollection. The only usage-shaped content is a negative constraint ('advanced parameters ... not yet available'), which tells the agent what it cannot do rather than when to reach for it.

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