get_portfolio

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

Annotations declare readOnlyHint=true confirming safe read operation. Description adds domain context (T-Investments) but does not disclose what portfolio data includes (cash, securities, totals) or behavioral details like caching.

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?

Single sentence with action front-loaded. Appropriate length for the tool's complexity, though extremely minimal with no elaboration on scope or contents of the returned portfolio.

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?

Sufficient for a simple 2-parameter read operation with good annotations. Identifies the brokerage system context. Lacks completeness regarding output structure, but no output schema exists to reference.

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 has 100% description coverage with clear Russian descriptions (accountId references get_accounts, tickers explains filtering). Description adds no parameter details, but baseline 3 is appropriate given complete schema documentation.

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?

Uses specific verb 'получить' (get) with resource 'портфель клиента' (client portfolio) and identifies the domain 'Т-Инвестиции' (T-Investments). However, it does not distinguish from sibling tool 'get_positions' which likely returns similar holdings data.

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?

No explicit guidance on when to use this versus 'get_positions' or other sibling tools. No mention of prerequisites or workflow (though the accountId schema description references get_accounts).

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