CDP set collateral config

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

No annotations are provided, so the description carries full burden. 'set' implies a write/mutation operation, but the description doesn't disclose critical behavioral traits: whether this requires admin permissions, if changes are irreversible, what happens to existing CDPs using this collateral, or any rate limits/constraints. For a 9-parameter configuration tool with no annotation coverage, this is severely inadequate.

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, efficient sentence ('Admin: set collateral parameters.') with no wasted words. However, it's overly terse given the tool's complexity—front-loading is good, but it under-specifies rather than being concise.

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 high complexity (9 required parameters), 0% schema description coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't explain the tool's purpose in context, parameter meanings, behavioral implications, or output. For a configuration tool in a DeFi/blockchain context, this leaves the agent unable to use 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?

Schema description coverage is 0%, meaning none of the 9 parameters have descriptions in the schema. The tool description provides no information about parameters beyond 'collateral parameters', failing to explain what 'asset', 'liquidationRatio', 'stabilityFeeRate', etc., represent or their expected formats. This leaves all parameters semantically undocumented.

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 'Admin: set collateral parameters' restates the title ('CDP set collateral config') and name ('set-collateral-config') without adding specificity. It mentions 'collateral parameters' but doesn't clarify what a CDP is or what 'set' entails operationally. Compared to siblings like 'strato.cdp.set-collateral-config-batch', it doesn't distinguish itself as the single-asset version.

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 on when to use this tool versus alternatives like 'strato.cdp.set-collateral-config-batch' for batch operations or 'strato.cdp.set-asset-paused' for pausing. The 'Admin:' prefix implies administrative privileges but doesn't state prerequisites or exclusions. The description lacks any context for tool selection.

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