fetch_account_summary

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

States 'Read-only' and 'live balance' indicating no mutation and real-time data, but lacks details on rate limits, authentication needs, error handling, or data freshness. With no annotations, description carries full burden but provides only minimal behavioral context.

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?

Single sentence, front-loaded with action and resource. No wasted words, efficient and clear.

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, so description should detail return structure. Lists three components but doesn't specify if response is single object or array for multiple accounts. Lacks error conditions or pagination info. Adequate but not fully complete.

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?

Description adds meaning beyond the input schema by specifying the returned data (balance, account type, linked instruments). Schema has 100% coverage, so baseline is 3; the additional context justifies a 4.

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?

Description clearly states verb 'fetches', resource 'account summary', and scope 'live balance, account type, and linked instruments'. Distinguishes from sibling tools like fetch_transaction_stream and classify_transaction_batch.

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?

Implied usage for fetching account summary but no explicit guidance on when to use this tool vs alternatives like fetch_transaction_stream. No exclusions or alternative tool names mentioned.

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