get_portfolio_summary

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

The description discloses authenticated access (requires IWMM_API_KEY), tier-dependent output, and the specific data fields returned. With no annotations, this is good behavioral disclosure, though it omits read-only nature and rate limits.

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 sentences efficiently convey purpose, output, tier differences, and authentication requirement. No wasted words.

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?

For a simple read-only tool with no parameters and no output schema, the description adequately covers what the agent needs: authentication, data content, and tier restrictions. Minor omission: whether output is single object or array.

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 per guidelines the baseline is 4. The description adds no parameter info, but none is needed.

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 retrieves a portfolio summary with specific fields (current value, total invested, unrealized P&L, ROI, counts). It distinguishes from siblings like get_portfolio_breakdown (detailed allocation) and get_portfolio_history (time-series).

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 usage context is implied: for a quick overall snapshot. It mentions free vs premium tiers, clarifying data availability. However, it does not explicitly state when to use over alternatives or provide exclusions.

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