Performance Bigpipe Enable

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about the performance impact of turning BigPipe on or off, required permissions, whether the change is persisted, or that this is a mutation.

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?

A single terse sentence with zero padding. It is not under-specified to the point of being unclear, but its brevity comes at the cost of all supporting context.

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?

An output schema exists so return values need not be explained, but for a config-mutating tool with no annotations and no parameter documentation, the description should at least state permissions or the nature of the change. It leaves the agent without enough to invoke it confidently.

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 0%, so the single 'enable' boolean is undocumented in the schema. The description's 'enable or disable' maps to the param name but adds no meaning about the default (true) or the effect of each value. With only one simple param, this is borderline adequate.

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 action (enable/disable) on a specific resource (BigPipe), which is enough to distinguish it from the sibling performance_bigpipe_status (which reads state rather than toggling it). However, it never explicitly names that sibling or clarifies the split between the read and toggle tools.

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?

No when-to-use guidance, no prerequisites, no mention of when toggling is appropriate versus querying status. The agent must infer usage entirely from the tool name.

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