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

The description claims the tool 'builds and rebalances' a portfolio, implying write/mutation operations. However, annotations declare readOnlyHint=true and destructiveHint=false, indicating a read-only, idempotent operation. This direct contradiction misleads agents about the tool's behavior.

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 two sentences, front-loaded with the purpose, and contains no unnecessary words. Every sentence adds value and is efficiently structured.

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?

Despite good purpose clarity, the description is incomplete. It omits details about the output (no output schema) and fails to disclose the read-only nature contradicting annotations. Given the contradiction and missing return value info, the description does not fully equip an agent to use the tool 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 100%, so the schema already explains all parameters. The description adds no additional parameter details beyond what the schema provides, meeting the baseline for this dimension.

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 builds and rebalances a diversified portfolio to maximize recurring income, with a specific verb and resource. It distinguishes from the sibling 'analyze_yield_opportunities' by focusing on actual portfolio construction rather than just analysis.

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 'Use when the user wants to achieve financial independence... or optimize an existing portfolio for yield.' This provides clear context for when to invoke the tool, though it does not explicitly exclude use cases or mention the sibling tool as an alternative.

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