Create Bruno request

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

With no annotations provided, the description carries the behavioral burden. It does disclose two non-obvious file behaviors: missing parent folders are auto-created and existing files are not overwritten. But it omits what happens when a file already exists (error vs no-op), what the successful response contains, and any other side effects beyond file creation.

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 one front-loaded sentence that conveys the essential action plus two important edge-case behaviors with no filler. Every clause earns its place.

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 17-parameter mutation tool with no output schema and no annotations, the description is not fully complete: it lacks success/error signaling, what happens on an existing-file conflict, and explicit routing to bruno_update_request. The schema compensates for parameter details, and the description covers the most important file-system behaviors, so it is adequate but has clear gaps.

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 high at 88%, so the schema already documents most parameters and the baseline is 3. The description adds extra meaning by clarifying request-path behavior: nested parent folders are automatically created and an existing target file is not overwritten, which is not stated in the schema's parameter descriptions.

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 names a concrete action ('Create') and a concrete resource ('Bruno HTTP request YAML file'), so an agent immediately knows what the tool does. The phrase 'existing files are not overwritten' also distinguishes it from bruno_update_request, which is the main sibling it could be confused with.

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 'create' verb and the warning that existing files are not overwritten imply this tool is for new request files, giving some usage context. However, it never explicitly says to use bruno_update_request when the target already exists, nor does it state any other when-to-use/when-not-to-use guidance relative to sibling tools.

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