get_portfolio_sector_exposure

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

No annotations are provided, so the description carries the full burden. It discloses read-only behavior, deterministic calculation, and detailed output structure (total market value, sector/symbol breakdown, concentration_flags at 25%). This provides meaningful behavioral context beyond a bare tool name.

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?

Three sentences, front-loaded with the action verb, and every sentence adds distinct information: computation purpose, return contents, and behavioral traits. 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 no-parameter, read-only analytical tool, the description specifies the threshold, the output components, and the computational nature. It is complete enough to invoke correctly without additional context.

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?

The input schema has zero parameters and coverage is 100%, so the baseline is 4. The description adds value by explaining what the zero-argument call returns, which is sufficient for invocation.

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 a specific verb ('Compute') and identifies a clear resource ('sector/symbol concentration for the current portfolio'), which distinguishes it from sibling tools like get_account_positions and get_market_snapshot.

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 context is clear that this tool is for concentration analytics on the current portfolio, but it does not explicitly name alternatives or state when not to use it. The 'deterministic calculation, not a model estimate' note adds useful selection context.

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