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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds behavioral details: lists transaction types, returned fields (quantity, value, amount, netAmount, expenses), and bulk support. No contradictions.

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 paragraphs, front-loaded with purpose and key details. No fluff. Efficiently covers purpose, fields, prerequisite, and bulk mode.

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?

Output schema absent, but description enumerates many return fields and provides prerequisite. Missing pagination behavior and error handling. Adequate for a read-only list tool with good annotations.

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?

With 0% schema description coverage, description must compensate. Only investment_id and investment_ids are described; page and page_size are omitted entirely, leaving the agent unaware of pagination support.

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 returns movement history for investment positions (BUY/SELL/TAX/INTEREST/AMORTIZATION/TRANSFER). It distinguishes from siblings by specifying investment-specific transactions and referencing openfinance_list_investments as a prerequisite.

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?

Provides clear context: use after openfinance_list_investments to get investment_id. Mentions bulk support with investment_ids. Does not explicitly contrast with openfinance_list_transactions or state when not to use.

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