create_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a new collection, implying a write operation, but does not mention permissions required, whether the operation is idempotent, error handling, or what happens if the workspace ID is invalid. This lack of detail is a significant gap 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 a single, efficient sentence that front-loads the core purpose. It avoids unnecessary words, though it could be slightly more structured by separating format details into a second sentence for clarity. Overall, it is appropriately concise for the tool's complexity.

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 that this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like authentication needs, error responses, or the structure of the created collection. For a tool that creates resources in a workspace, more context is needed to guide effective use.

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?

The schema description coverage is 100%, so the input schema fully documents the parameters. The description adds minimal value by implying the collection must be in Postman Collection v2.1.0 format, which aligns with the schema's description of 'collection details in Postman Collection Format v2.1'. No additional parameter semantics are provided beyond what the schema already covers.

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 ('Create a new collection') and the resource ('in a workspace'), and specifies the supported format ('Postman Collection v2.1.0 format'). However, it does not explicitly differentiate this tool from sibling tools like 'create_collection_folder' or 'create_collection_request', which might create similar collections in different contexts or with different structures.

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 no guidance on when to use this tool versus alternatives, such as 'create_collection_folder' for nested structures or 'fork_collection' for duplicating existing ones. It mentions workspace context but does not specify prerequisites, exclusions, or typical use cases, leaving the agent to infer usage from the tool name alone.

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