get_fund_portfolio

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

With no annotations, the description carries the full burden and delivers real behavioral context: corporate actions are flagged rather than asserted as trades, market-cap allocation is deliberately reported as null instead of guessed, and coverage depends on which AMC adapters have run. These are exactly the caveats an agent needs to avoid misreading output. It does not cover permissions or rate limits, but the data-quality disclosures are strong.

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 purpose sentence is front-loaded and the remaining lines are a tight parameter glossary with no filler. Slightly dense, but every line carries information.

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 7-parameter, no-annotation, no-output-schema tool, the definition covers the highest-value behavior and three parameters but leaves the semantics of as_of, provenance, holdings_limit, and scheme_ids entirely unspecified, which is a meaningful gap for an agent invoking it precisely.

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 0%, so the description must compensate, and it partially does: it enumerates the valid 'sections' values, the 'history' values plus the persistence-table requirement, and 'compare_to' accepted forms. However, four parameters (as_of, provenance, scheme_ids, holdings_limit) get no explanation in either schema or description.

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 names a specific resource set (holdings, allocations, month-over-month change detection) and scope (one or more schemes), so an agent knows this is the portfolio-composition tool rather than the performance or profile tool. It stops short of explicitly contrasting itself with siblings like get_fund_performance or get_fund_profile.

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?

There is no explicit statement of when to use this tool versus the sibling tools. The only conditional guidance ('required for the persistence table', 'null to skip change detection') is about parameter wiring, not tool selection.

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