Performance Bigpipe Status

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

With no annotations provided, the description carries the full behavioral burden. 'Check' weakly implies a read-only operation, but it does not state whether authentication or admin permissions are required, whether any side effects occur, or what the returned status/configuration includes. This is a significant gap for a tool with zero annotation coverage.

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, front-loaded sentence with no redundant or filler content. Every word contributes to conveying the tool's purpose.

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?

The tool is simple (no parameters, output schema exists) and the description states its purpose, so it is minimally adequate for an agent to invoke it. However, with no annotations and only a terse sentence, it omits any behavioral context such as read-only nature, permissions, or how it relates to sibling tools, leaving 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?

The tool takes zero parameters, so the baseline score of 4 applies. The description correctly adds no parameter information because none is needed, and the empty schema is fully consistent with a parameterless status check.

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 gives a specific verb ('Check') and resource ('BigPipe status and configuration'), which is clear enough to distinguish it from the sibling 'performance_bigpipe_enable' by implication (read vs. write). It does not explicitly name the alternative sibling, so it falls short of the highest clarity score.

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?

Usage is implied by the verb 'Check' for a status/configuration tool, but there is no explicit guidance on when to use this versus alternatives like 'performance_bigpipe_enable' or 'performance_page_load_analyze'. No prerequisites or exclusions are stated.

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