get_portfolio_summary

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

With no annotations, the description carries full behavioral disclosure burden. It only states the purpose but omits details like read-only nature, required permissions, rate limits, or any side effects. For a data retrieval tool, basic safety context is missing.

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?

A single sentence with zero wasted words. Front-loaded with the action 'Get a summary'. Every word is necessary.

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?

The tool is simple with no parameters and no output schema. The description is adequate but could be more complete by hinting at the return structure (e.g., total value, asset allocation). Given sibling tools for granular balances, a note on what 'summary' includes would improve completeness.

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?

There are zero parameters, so schema description coverage is 100% vacuously. Per guidelines, baseline is 4 for no parameters. The description adds no parameter info since none exist.

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 'Get a summary of all portfolio holdings and balances' clearly states the verb (Get) and resource (summary of all portfolio holdings and balances). It distinguishes from siblings like get_all_portfolios (which likely lists portfolios) and granular balance getters (e.g., get_bond_balances).

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 implies usage for obtaining a broad overview but provides no explicit guidance on when to use this tool versus alternatives like get_all_portfolios or specific balance tools. No when-not or alternative recommendations.

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