CDP global pause

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Admin' and 'toggle', implying it's a mutation that requires elevated permissions, but fails to detail critical aspects like what 'global CDP pause' entails (e.g., pausing all CDP operations system-wide), potential side effects, whether the change is reversible, or any rate limits or authentication requirements. The description is too vague for a tool that likely has significant system impact.

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 just three words, making it front-loaded and efficient. However, this brevity comes at the cost of clarity and completeness, as it omits necessary details for proper tool usage. While it avoids waste, it may be overly terse for a tool with potential system-wide impact.

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?

Given the complexity implied by 'global CDP pause' (likely a critical admin function), the lack of annotations, no output schema, and minimal parameter documentation, the description is inadequate. It doesn't explain the tool's effects, return values, or how it integrates with the broader system (e.g., sibling tools like 'strato.cdp.set-asset-paused'), leaving significant gaps for an AI agent to understand and invoke it correctly.

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 1 parameter with 0% description coverage, and the tool description provides no information about the 'isPaused' parameter. It doesn't explain what the boolean value represents (e.g., true to pause, false to unpause), default behavior, or any constraints. This leaves the parameter's meaning ambiguous, failing to compensate for the lack of schema documentation.

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 ('toggle global CDP pause') and identifies it as an admin function. It specifies the resource ('global CDP pause'), making the purpose understandable. However, it doesn't explicitly differentiate from the sibling tool 'strato.cdp.set-asset-paused', which appears to be a similar pause function but for individual assets rather than globally.

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 provides minimal guidance by labeling it as 'Admin', implying it requires admin privileges. However, it offers no explicit guidance on when to use this tool versus alternatives like 'strato.cdp.set-asset-paused' or other pause-related tools in the sibling list, nor does it mention any prerequisites or exclusions beyond the admin hint.

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