createSpec

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

Annotations indicate readOnlyHint=false and destructiveHint=false, confirming this is a write operation. The description adds behavioral context beyond annotations: file size limit (10 MB), auto-folder creation on '/' in path, and the constraint that multi-file specs require exactly one ROOT file. No contradictions with 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 well-structured with a main sentence and a bulleted note section. It is fairly concise, though the note about supported formats could be integrated more tightly. Every sentence adds value, and the structure aids readability.

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 lacks information about the return value (e.g., created spec ID or object). While it covers constraints and file types, it does not mention what the agent should expect as a response, which is a gap for a creation tool with four required parameters.

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 baseline is 3. The description adds marginal value: it notes that files cannot exceed 10 MB and that path with '/' creates folders, but these details are not in the schema. However, the parameter descriptions in the schema already cover the essential semantics adequately.

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 creates an API specification in Postman's Spec Hub, distinguishing it from sibling tools like createSpecFile (which likely creates files within a spec) and updateSpecProperties. The verb 'creates' and resource 'API specification' are explicit, and the ability to handle single or multi-file specs adds specificity.

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 useful constraints (supported formats, file path behavior, multi-file root rule, size limit) but does not explicitly guide when to use this tool versus alternatives like createSpecFile or updateSpecProperties. It implies usage for creating new specs but lacks direct comparison with siblings.

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