get_portfolio

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

Annotations already declare readOnlyHint=true, and the description's 'Get' is consistent. The description adds valuable context beyond annotations by detailing the specific data returned (TRY value, P/L, cash, buying power) and the account split (Turkish vs. US). It does not disclose rate limits or error conditions, but the read-only nature is covered.

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, well-structured sentence that front-loads the main purpose ('Get overall portfolio value'), then lists the specifics. Every word earns its place; no fluff, no redundancy.

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 tool without an output schema, the description does a good job covering what is returned. It lists all major output components and account types. However, it could be more precise about currencies for cash balances or whether the output is a snapshot, but this is a minor gap for such a simple tool.

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 properties, so there are no parameters to describe. The baseline for 0 params is 4, and the description does not attempt to explain parameters, which is appropriate.

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 states the tool's function with a specific verb ('Get') and resource ('overall portfolio value'), and enumerates the exact outputs: value in TRY, today's profit/loss, cash balances, and buying power for both Turkish and US accounts. This distinguishes it from sibling tools like get_assets, which focus on individual assets.

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 provides no explicit guidance on when to use this tool relative to others, nor any exclusions or alternatives. While it is implied for portfolio overview, it does not mention that get_assets handles asset-level detail or that buy/sell tools handle transactions, leaving usage to inference.

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