Run Bruno collection

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

With no annotations, the description carries the full burden and does well: it discloses the security mechanism (secrets read from the MCP server process, injected via a temporary private --env-file, never through CLI arguments) and the workspace-root path restriction. It does not state side effects of actually executing requests (real network calls to target systems, possible mutation, timeouts, or failure semantics), which is a notable gap for an execution 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?

Front-loaded with the action and return shape, followed by parameter and safety guidance. Four dense sentences with little waste, though the phrasing is tightly packed and could be marginally trimmed.

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 4-param execution tool with no output schema or annotations, the description covers what the tool does, its return shape, secret handling, and path constraints. It omits runtime behavior such as failure/timeout handling and whether execution is destructive to the target system, which leaves a small but real gap.

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 the baseline is 3. The description adds meaning beyond the schema by explaining the secret-handling protocol for `inherited_variables` and the workspace-root constraint on `collection`, which the schema does not convey.

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?

States a specific verb and resource ('Run a Bruno collection with the local `bru` CLI') plus the return shape ('normalized JSON with success, request summary, per-request details, failures, and execution timings'). An agent can distinguish it from the sibling run-filter-scenarios / run-full-validation tools by the explicit reference to running a whole collection.

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?

Gives clear conditional guidance: pass KEY=value variables normally, but for secrets pass only names via `inherited_variables`, and collection paths must stay inside configured workspace roots. It stops short of naming alternative tools (e.g. run-filter-scenarios) or stating when not to use this one, so it is context-rich but not a full routing guide.

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