get_portfolio_breakdown_cards

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

With no annotations, the description carries the full burden. It discloses the premium-gating and API key requirement, but lacks details on read-only behavior, rate limits, or error conditions, leaving gaps.

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 one sentence with a parenthetical and two brief notes, front-loading the core action and adding essential constraints without waste.

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?

Without an output schema, the description gives no hint about the return format (e.g., list of card objects, pagination), which is a notable gap for a drill-down tool that likely returns a collection.

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 coverage is 100%, so parameters are documented. The description adds relational context by explaining that 'by' and 'key' must match the get_portfolio_breakdown call and that 'colors' is only for specific dimensions, enhancing understanding.

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 uses specific verb and resource: 'Get the cards inside one slice of a portfolio breakdown' and clearly distinguishes it from the parent tool get_portfolio_breakdown by calling it a 'drill-down'.

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 the tool should be used after get_portfolio_breakdown and states it is premium-gated requiring IWMM_API_KEY, providing clear context. However, it does not explicitly list when not to use or alternatives.

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