pivot_list_pivots

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. 'List pivots' implies a read-only operation but gives no information about prerequisites, output format, or whether it reflects current active pivots vs. configured pivots. This is minimal and insufficient for a tool with no output schema.

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 extremely concise with no filler words, but it borders on under-specification. It is front-loaded and easy to read, yet the single phrase adds little beyond the tool name.

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 and no annotations, the description leaves important questions unanswered: what exactly is a pivot, what fields are returned, and how does this relate to tunnels/stops/adds. For a nullary tool in a larger pivot management family, this is not complete.

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 input schema has zero parameters and 100% coverage, so no parameter explanation is needed. The description does not need to add parameter semantics.

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 'List pivots.' is a direct restatement of the tool name pivot_list_pivots and provides no additional scope or detail. It also fails to distinguish this from sibling pivot_list_tunnels, making it tautological rather than explanatory.

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 guidance is provided about when to call this tool, what a pivot is in this context, or how it differs from pivot_list_tunnels and other pivot management tools. The description simply states the action without context or alternatives.

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