runCollection

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

Annotations indicate this is a non-destructive, idempotent operation (readOnlyHint: false, destructiveHint: false, idempotentHint: true). The description adds value by mentioning it returns 'detailed test results and execution statistics' and notes missing advanced features, but does not disclose rate limits, authentication needs, or specific behavioral traits beyond annotations.

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 front-loaded with the core purpose in the first sentence, followed by supportive details and a limitation note. Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding.

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?

Given the tool's complexity (9 parameters, execution-focused) and lack of output schema, the description adequately covers purpose, usage context, and limitations. However, it could be more complete by hinting at the output format (e.g., 'returns a report object') to compensate for the missing output schema, though annotations provide some behavioral context.

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%, so parameters are fully documented in the schema. The description adds minimal semantics by mentioning 'optional environment for variable substitution' (hinting at environmentId) and 'advanced parameters... not yet available' (implying limitations), but does not provide additional meaning beyond the schema's detailed descriptions.

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 action ('Runs a Postman collection by ID') and the resource ('Postman collection'), specifying it provides 'detailed test results and execution statistics'. It distinguishes from sibling tools like 'getCollection' (which retrieves metadata) by emphasizing execution with results.

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 provides clear context for usage ('Supports optional environment for variable substitution') and notes limitations ('Advanced parameters like custom delays and other runtime options are not yet available'), which helps guide when to use it. However, it does not explicitly compare to alternatives like 'syncCollectionWithSpec' or state when not to use it.

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