get_portfolio_overview

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

No annotations are present, so the description must fully communicate behavioral traits. It only states 'comprehensive portfolio overview' without clarifying whether this is a read-only operation, what data is included, whether network parameter affects behavior, or any rate limits. This is a substantial gap.

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, efficient sentence with no filler, and the core purpose is front-loaded. While it sacrifices detail, it earns high marks for conciseness.

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 lack of output schema and annotations, the description needs to explain return values and behavioral scope. It does not mention what 'comprehensive' includes, how network selection affects results, or how this tool differs from the many portfolio-related siblings. This is inadequate for correct tool selection.

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% for both address and network, so the schema carries the meaning. The description adds no extra layer of context beyond the schema, keeping it at the baseline 3.

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 action ('Get') and resource ('portfolio overview') for an address, making the core purpose understandable. However, it does not differentiate from siblings like get_wallet_portfolio, get_multichain_portfolio, or portfolio_get_summary, all of which sound similar in scope.

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. The description does not mention use cases, prerequisites, or exclusions, leaving the agent without direction for tool selection.

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