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

The description lacks detail beyond stating it uses 'latest account records.' With no annotations, it fails to disclose auth needs, caching, error behavior, or what accounts are included. However, the tool name implies read-only, so transparency is adequate but incomplete.

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 a single sentence with no wasted words, front-loading the verb 'Return.' It could add brief parameter guidance without losing conciseness, but overall structure is good.

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?

Given the tool's simplicity (1 param, no output schema, no annotations), the description covers the core action but omits usage guidelines, parameter details, and behavioral context. It is minimally acceptable but leaves gaps.

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?

The schema defines a single 'currency' parameter but the description does not mention it at all. Schema coverage is 0%, so the description should clarify format (e.g., ISO 4217), valid values, or impact. It provides zero parameter insight.

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 the current total portfolio value using latest account records. It uses a specific verb ('Return') and resource ('total portfolio value'), and is easily distinguished from siblings like get_portfolio_performance or get_account_allocation.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context that would help an agent decide between this and sibling tools like get_net_worth_summary or get_portfolio_performance.

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