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

Annotations indicate a write operation (readOnlyHint=false) but no destructive behavior (destructiveHint=false). The description adds significant transparency: it details the bridging from Base to Solana via CCTP, swap on Jupiter, and minting of a soul-bound gitStock token. It also reveals the asynchronous authorization step (returns confirm_code for GitHub posting). No contradiction with annotations.

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 three sentences, each earning its place. The first sentence states the main action. The second explains the process. The third explains the return value and user action needed. No fluff.

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 tool with no output schema, the description covers all key aspects: input parameters (implicitly via schema), process steps, and return value (confirm_code) with required user action. It is complete for an agent to decide and invoke.

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 100%, so the schema already documents each parameter. The description does not add new meaning beyond confirming that usdc_amount is from vault balance, which is already in the schema. Baseline 3 is appropriate.

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: 'Buy an Ondo tokenized stock using USDC from the user's Gitbank vault.' The verb 'Buy' and resource 'Ondo tokenized stock' are specific. It distinguishes from sibling tools like request_sell_stock and request_deposit by describing the unique multi-step flow (bridge, swap, mint).

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 explicitly states when to use: to buy stock using USDC from the vault. It does not explicitly list when not to use, but the sibling names provide contrast. The context (requires GitHub username, uses vault balance) gives clear guidance.

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