sigmavue_portfolio

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

No annotations exist, so the description bears full responsibility. It states the tool provides 'Current open positions plus a rollup summary', implying a read operation, but fails to disclose whether it is destructive, requires authentication, or has rate limits. The term 'rollup summary' is vague, and no details about data freshness, pagination, or response size are given.

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 clear sentence that front-loads the primary function and mentions the optional parameters. No extra words; every part is necessary. It is exceptionally concise.

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 the tool has only two optional parameters and an output schema exists, the description captures the core purpose. However, it lacks explanation of the 'rollup summary' and whether the positions include historical data. While the output schema may fill gaps, the description could be more informative about what the return data represents.

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 two optional parameters with 0% description coverage. The description adds that they are 'selectors' and names them as 'account_id' and position 'status_filter', clarifying their purpose as filters. However, it does not specify allowed values, formats, or behavior when omitted. The addition of 'Optional' helps but is minimal.

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 indicates the tool returns 'Current open positions plus a rollup summary'. It identifies the resource (positions/portfolio) and the action (retrieve/summarize). While no explicit verb is used, the noun phrase is unambiguous. Sibling tools like sigmavue_accounts_list or sigmavue_trade_execute show different domains, so this tool is sufficiently distinguished.

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 guidance on when to use this tool versus alternatives. The description does not mention prerequisites, typical use cases, or when to avoid it. Users are left to infer that it's for viewing portfolio positions, but there is no explicit context or comparison to sibling tools.

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