broker_quote_sell

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

The description mentions it creates a 'proforma quote' and is tagged '[PRIVATE]', but with no annotations, it lacks details on idempotency, expiration, or side effects. It does not confirm whether the operation is read-only or if it modifies state.

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 concise, front-loading the main action in a single sentence. Additional context (pocket IDs, required confirmation, private tag) is included without redundancy, though a more structured format could improve readability.

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?

No output schema is provided, and the description does not explain the return value (e.g., quote ID, expiration, prices). Given the tool requires a subsequent confirmation step, describing the output is important for the agent to proceed 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 coverage is 100%, so the schema documents each parameter. The description adds value by directing users to wallet_get_pockets for finding pocket IDs, but does not elaborate on amount format or other parameter specifics beyond the schema.

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's purpose: 'Sell cryptocurrency to receive fiat balance in a pocket. Creates a proforma quote.' It uses specific verbs and resources, and distinguishes itself from sibling tools like broker_confirm_quote (confirmation step) and broker_quote_buy.

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 labels this as 'STEP 1' and explicitly states 'REQUIRES subsequent confirmation with broker_confirm_quote.' It also instructs users to use wallet_get_pockets to find pocket IDs, providing clear prerequisites. However, it does not explicitly state when not to use this tool.

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