Get Portfolio Details

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

Annotations already communicate readOnly, idempotent, and non-destructive behavior. The description reinforces 'Retrieves' and mentions a dictionary return value, but adds little beyond that; no auth needs, rate limits, or side-effect context is provided. Since annotations carry the safety profile, this is adequate but not enriched.

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 repeats itself three times: the first sentence, the second sentence, and the 'Returns' block all say essentially the same thing. While the opening is front-loaded, the redundancy means several sentences do not earn their place.

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?

With no parameters, strongly safety-relevant annotations, and an output schema present, the description needs to do very little beyond identifying the tool's scope. It states the main content areas, so an agent can understand what the call returns. The only real gap is sibling differentiation, already penalized in usage guidelines.

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 tool has zero parameters and schema description coverage is 100%, so there is nothing meaningful for the description to add. It correctly avoids inventing parameter context, meeting the baseline for parameter-free tools.

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 clear verb-resource structure: 'Get comprehensive portfolio details including accounts, positions, and summary.' The content scope is stated, but it does not explicitly distinguish this aggregate tool from closely related siblings like get_accounts, get_portfolio_holdings, or get_portfolio_performance.

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 guidance on when to use this tool versus alternatives. The phrases 'complete overview' and 'comprehensive portfolio details' imply high-level use, but there are no explicit conditions, exclusions, or references to sibling tools, so an agent gets no selection guidance.

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