unstake_quote

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

No annotations exist, so the description must disclose behavioral traits. It states the tool retrieves a quote but doesn't confirm it's read-only, note permissions, or mention side effects. Minimal transparency beyond the basic action.

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?

Two concise sentences that front-load the purpose and then state expectations. No unnecessary words or redundant information.

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?

While the tool has an output schema, the description omits key context: it doesn't explain the role of an unstake quote in the staking workflow (e.g., obtaining a quote before executing unstake_transaction) or what the returned SwapQuoteRequestContainer contains.

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 description adds no extra meaning beyond the input schema for the single parameter. It repeats the container type but doesn't clarify parameter usage, format, or relationships. Schema description coverage is 0%, and the description doesn't compensate.

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 tool retrieves an unstake quote, differentiating it from sibling tools like stake_quote (for staking) and swap_quote (for swapping). The verb 'retrieve' and resource 'unstake quote' are specific and unambiguous.

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 explicit guidance on when to use this tool versus alternatives. The name and context suggest it's for unstaking, but the description doesn't explain the workflow (e.g., use this before unstake_transaction) or distinguish from similar quote tools.

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