Portfolio allocation

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

Annotations already declare readOnly=true, idempotent=true, openWorld=true, and non-destructive, so the safety profile is covered. The description adds useful behavioral detail about data provenance and bucket semantics, which is genuinely beyond the annotations. However, it omits the US/UAE truncation trigger ('at most 30 holdings, heaviest first') as a caveat only in passing and says nothing about empty-portfolio behavior or response shape.

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 single dense sentence is packed with parenthetical caveats and overlapping index-membership trivia ('they overlap and do not sum to 100%') that cost reading effort disproportionate to the value delivered. Front-loaded subject is fine, but the mid-clause clutter hurts scannability.

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?

Covers market-specific data sources and bucketing rules, which is meaningful context for a read-only aggregation tool. But with no output schema and no response-shape hint, an agent still cannot predict the return structure well enough to chain results reliably.

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% and the single enum parameter is fully documented in the schema. The description implies market-specific output differences but adds no syntax or format detail beyond what the schema's enum description already provides. Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb+resource (allocation of a portfolio's holdings by asset class and sector) and clearly differentiates its output shape from siblings like get_account_positions or get_portfolio_performance. It is dense but an agent can tell what it returns without opening a schema.

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 when the output differs by market (Egypt vs US/UAE/simulator behavior) but never states when to prefer this tool over siblings like get_portfolio_performance or get_account_summary. The market-dependent behavior hints at usage context but no alternatives or exclusions are named.

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