Stream SAP data via WebSocket

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't mention whether this is a read-only or destructive operation, what authentication might be required, whether it establishes persistent connections, what happens when streaming stops, or any rate limits. For a WebSocket streaming tool with 8 parameters, this complete lack of behavioral information is inadequate.

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?

While technically concise with just 4 words, this represents under-specification rather than effective brevity. The single phrase doesn't earn its place by providing meaningful information beyond what's already in the name and title. For a complex tool with 8 parameters and WebSocket functionality, this level of conciseness is insufficient rather than efficient.

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's complexity (WebSocket streaming with 8 parameters, no output schema, and no annotations), the description is completely inadequate. It doesn't explain what the tool returns, how streaming data is formatted, what happens with different actions, or any operational considerations. The description fails to provide the context needed for an agent to understand and use this tool effectively.

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 schema has 100% description coverage, so all parameters are documented in the structured schema. The description adds no additional parameter information beyond what's already in the schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no parameter information in the description, which applies here.

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?

Tautological: description restates name/title.

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 absolutely no guidance about when to use this tool versus alternatives. With 18 sibling tools including various SAP-related operations, there's no indication of appropriate contexts, prerequisites, or comparisons to tools like 'discover-service-entities' or 'sap-smart-query'. The agent receives no help in determining when WebSocket streaming is the right approach.

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