Create Bruno Collection

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

With no annotations, the description carries the full burden. It discloses key side effects: the collection is added to the workspace registry, and list_collections reads that registry rather than the disk. It also explains the result indicates registration status and failure reasons. This is unusually transparent for a creation 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 concise yet packed with necessary information. Every sentence earns its place: definition, path behavior, registry warning, and result explanation. It is well-structured and easy to parse.

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 tool with side effects and a registry integration, the description covers all essential aspects: creation location, naming, registration behavior, and result content. It also explains the default workspace path. Without an output schema, the description still gives a sufficient picture of what to expect.

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 only 38%, so the description must compensate. It does so by explaining outputPath's parent-directory semantics with a concrete example and clarifying how registerInWorkspace and workspacePath interact with the registry. Other parameters like format, ignore, baseUrl, and description remain simple, but the critical, error-prone ones are well covered.

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 it creates a new Bruno API testing collection, with a specific verb and resource. It distinguishes itself from sibling tools like delete_collection and list_collections by focusing on the creation side-effect and registry integration.

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 gives clear context on usage, including the exact path semantics and the registry behavior that affects visibility. It does not explicitly mention alternatives like create_crud_requests, but it provides enough guidance on how to operate correctly, including a 'do not' warning about duplicating the collection name.

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