get_my_portfolio

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions the output fields (balance, equity, etc.), but does not clarify if the summary is real-time or cached, whether all accounts are included, or any authentication requirements beyond the implicit need to be logged in.

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 a single, front-loaded sentence with no extraneous words. It efficiently conveys the purpose and key outputs, earning its 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?

Given no parameters, no output schema, and simple read semantics, the description provides sufficient information about the tool's return value. It could mention if there are any side effects or prerequisites, but the simplicity of the tool makes it reasonably complete.

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 no parameters, so the description adds meaning by specifying what the tool returns. With schema coverage at 100% (no params), a baseline of 4 is appropriate, and the description effectively communicates the tool's output.

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 clearly specifies the verb 'Get' and the resource 'your trading portfolio summary', listing concrete data points (balance, equity, PnL, open positions, win rate). This distinguishes it from sibling tools like get_my_positions (which likely returns only positions) or get_agent_stats (different scope).

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 is for retrieving a high-level portfolio overview, but it does not explicitly state when to use it over alternatives such as get_my_positions or get_agent_stats. No usage conditions or exclusions are provided.

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