Create Bruno Collection

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

With no annotations, the description must carry the full burden of disclosing side effects and requirements. It states a creation action but does not mention permissions, whether existing collections are overwritten, what 'configuration' includes, or what the return value/output is. This is a minimal disclosure 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 sentence with no wasted words, but it is under-specified for a tool with six parameters. It earns its place yet leaves critical information unstated, resulting in a structure that is concise but insufficiently informative.

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 complexity (6 parameters, no annotations, no output schema), the description is incomplete. It does not clarify the tool's role in a Bruno workflow, what the setup entails, or what the user should expect, making it inadequate for informed selection and invocation.

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 17% (only outputPath has a description), and the tool description adds no parameter details. The phrase 'with configuration' hints at parameters but does not explain their meaning, format, or defaults, failing to compensate for the low schema coverage.

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 Bruno API testing collection.' This distinguishes it from sibling tools like create_environment or create_request by explicitly naming the resource type. The phrase 'with configuration' is vague but not misleading.

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_request or create_test_suite. It does not mention prerequisites, common use cases, or any explicit exclusions, leaving the agent to infer from name alone.

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