CDP pause asset

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

With no annotations, the description carries full behavioral disclosure burden. 'toggle pause' implies a state mutation, but it doesn't specify permission requirements, side effects (e.g., impact on existing positions), reversibility, or error conditions. This is inadequate for an administrative mutation tool.

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?

Extremely concise at 6 words with zero wasted language. The structure is front-loaded with the core action ('toggle pause') followed by target and context. Every word earns its place.

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?

For an administrative mutation tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks behavioral context, parameter explanations, and output expectations, leaving significant gaps for agent understanding.

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 description must compensate but adds no parameter details. It doesn't explain what 'asset' represents (identifier format) or 'isPaused' semantics (true=pause, false=unpause). This leaves both parameters undocumented beyond basic types.

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 pause') and target ('collateral asset'), with 'Admin' indicating administrative context. It distinguishes from siblings like 'strato.cdp.set-global-paused' by specifying asset-level control, but doesn't explicitly contrast with other pause-related tools like 'strato.lending.pause'.

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 with 'Admin' hinting at permission requirements, but offers no explicit when-to-use rules, alternatives (e.g., vs. global pause), or prerequisites. It doesn't help an agent decide between this and sibling tools like 'strato.cdp.set-global-paused'.

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