Get Collection Statistics

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

No annotations are provided, so the description carries the burden. It adds a valuable behavioral disclosure: environmentDetails lists only the NAMES of variables, with values withheld. It also implies a read-only nature by describing the tool as collecting statistics, though it does not discuss side effects or error behavior.

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 three sentences, front-loaded with the main purpose, and each sentence adds substantive value: the overall statistics, the environmentDetails behavior, and the run_collection integration. There is no filler or redundant repetition of schema information.

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 sufficiently explains the key return sections (request counts by method, folders, environments, per-request file paths) and provides actionable cross-tool guidance. It gives enough detail for an agent to understand what the tool returns and how to use it effectively.

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 coverage is 100%: the only parameter, collectionPath, already has a full description in the schema including the direction to use the path returned by list_collections. The tool description adds no additional parameter-level meaning, so the baseline score of 3 applies.

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 ('Get statistics') and the resource ('a Bruno collection'), and enumerates what is included: request counts by method, folders, environments, and per-request details. This distinguishes it from sibling tools by framing it as a read-only summary/analysis tool.

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 concrete usage guidance by explaining how to use the output: use filePath values for run_collection and inspect environment variable names before merging with set_environment_variable. It does not explicitly state when not to use this tool or name direct alternatives, but the context is clear.

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