createCollection

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, covering the basic safety profile. The description adds the workspace default behavior, which is useful context beyond annotations. However, it doesn't disclose other behavioral traits like error handling, rate limits, or authentication requirements, leaving some gaps for a mutation tool.

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 appropriately sized with two sentences: one stating the purpose and schema format, and a note about workspace defaulting. It's front-loaded with the core action and includes a helpful note, though the schema link could be more concise. No wasted sentences, but minor verbosity in the link formatting.

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?

For a mutation tool with no output schema, complex nested parameters, and 50% schema coverage, the description is minimally adequate. It covers the purpose and a key behavioral note but lacks details on the 'collection' parameter, error handling, or response format. Given the complexity, more context would improve completeness, but it meets a basic threshold.

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 50%, with only the 'workspace' parameter documented in the schema. The description doesn't add any parameter-specific semantics beyond what's in the schema or annotations. It mentions the schema format but doesn't explain the 'collection' parameter's structure or requirements. Baseline 3 is appropriate given the partial schema coverage and lack of compensation in the description.

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 tool's purpose: 'Creates a collection using the Postman Collection v2.1.0 schema format.' It specifies the verb ('creates'), resource ('collection'), and format, but doesn't explicitly differentiate from sibling tools like 'createCollectionRequest' or 'duplicateCollection' beyond the schema reference.

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 note provides implicit guidance about workspace selection (defaults to oldest personal Internal workspace if omitted), which helps with usage context. However, it doesn't explicitly state when to use this tool versus alternatives like 'duplicateCollection' or 'generateCollection', nor does it mention prerequisites or exclusions.

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