cap_stream_portfolio

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

No annotations are provided, so the description must fully disclose behavior. It mentions streaming for a duration but does not explain connection lifecycle, resource usage, rate limits, or what happens after the duration ends. This is insufficient for a streaming tool.

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 minimal waste. However, it sacrifices important details for brevity, like explaining the second parameter.

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?

An output schema exists (though not shown), so return values need not be explained. However, the description lacks details on how the WebSocket stream works, when it terminates, and what constitutes a snapshot. It is adequate but not fully complete for a streaming tool with multiple siblings.

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 description coverage is 0%, so the description must explain both parameters. It only mentions duration_s implicitly through 'for duration_s seconds', but does not explain update_interval_s or clarify parameter units, defaults, or constraints.

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 verb 'Stream', the resource 'live portfolio snapshots for open positions', and the key parameter 'duration_s'. It also mentions 'WebSocket' to indicate the technology. This distinguishes it from sibling stream tools like cap_stream_alerts and cap_stream_prices.

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 usage for real-time streaming via WebSocket but does not explicitly state when to use this tool versus alternatives like cap_stream_prices or cap_stream_alerts. No guidance on prerequisites or when not to use it is provided.

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