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

With no annotations provided, the description carries the full behavioral burden and delivers extensively. It discloses the non-custodial security posture ('Barker NEVER broadcasts and never holds funds'), the exact return structure (transaction_request with chainId, from, to, data, value + route + risk summary + approval info), failure modes (POOL_NOT_FOUND, 409 POOL_AMBIGUOUS with candidates), the 'rejects ambiguity instead of guessing' policy, the paid $0.05/call cost, and the 'backend rejects a mismatch' cross-check behavior. Nothing is left to inference.

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 long but every sentence earns its place given the high-stakes money path — security posture, flow, identity rules, error behavior, and concrete examples are all load-bearing. It is front-loaded with the core action and prioritized with critical constraints near the top. Likely slightly overstuffed exactly where safety justifies it, so not a 5 but well above adequate.

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 a complex 7-parameter financial tool with no output schema and no annotations, the description is remarkably complete. It covers the return payload structure (compensating for the missing output schema), error semantics, dimensionality/decimals handling, cross-chain edge cases, and the full flow with sibling tools. An agent has everything needed to call 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 coverage is 100%, so the baseline is 3, and the description clearly adds value on top. It explains the amount vs amount_base_units mutual-exclusion and server-side conversion using the pool's own decimals, explains why signer_address is mandatory (it is the tx sender and share recipient — 'Barker can never infer or default it'), and clarifies when chain_id matters (same address on several chains). This goes beyond the raw property descriptions.

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 states a specific verb and resource ('buy an unsigned, ready-to-sign transaction that deposits into or redeems from a stablecoin vault') and clearly distinguishes this from siblings by placing it in an explicit flow (barker_yield_advisor → barker_executable_pools → this tool → user signs). It also clarifies what it is NOT (non-custodial, never broadcasts). An agent can immediately tell this apart from discovery/pricing tools like barker_executable_pools or barker_yield_advisor.

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?

Extremely explicit when-to-use guidance: names the flow context, states to use it when 'you already know the vault address' (no discovery call needed), gives concrete example prompts in both English and Chinese, and spells out constraints like 'vault shares always go to signer_address' and 'Same-chain only'. It also tells the agent what to NOT do (never accept symbols or asset-token addresses as identity) and states exclusions for alternatives.

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