schwab_stream_account_activity

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

With no annotations provided, the description must convey all behavioral traits. It implies a read operation via 'Get', but does not disclose details about streaming behavior (e.g., persistent connection, event frequency), authentication needs, or side effects. Sufficient for basic purpose but lacks depth.

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 that wastes no words. Every term ('Get', 'latest', 'account activity events', 'Schwab streaming') is purposeful and 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 no parameters and the existence of an output schema, the description is mostly complete. It clearly indicates what resource is retrieved. However, it could clarify 'latest' (e.g., last event vs. continuous stream) and whether authentication is required, but overall adequate for a simple streaming 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 parameters, so there is nothing to explain. Per guidelines, baseline for 0 parameters is 4. The description does not need to add parameter information.

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 'Get', the resource 'latest account activity events', and the source 'Schwab streaming'. It is specific and distinguishes itself from sibling tools like account_details or schwab_account by focusing on streaming events.

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 does not provide any guidance on when to use this tool vs. alternatives (e.g., non-streaming account endpoints). No exclusions or prerequisites are mentioned, leaving the agent without contextual cues for appropriate usage.

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