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

The description states it 'returns only stream contracts' suggesting a read operation, but annotations set readOnlyHint=false without clarification. The generic execution guidance (pricing, routing, signer boundary) is repetitive and does not disclose tool-specific behaviors like potential side effects, rate limits, or required permissions.

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 bloated with redundant SAP MCP execution guidance that appears verbatim in the schema description, repeating seven times across the description and schema. The first sentence is clear, but the extended generic block reduces conciseness and adds no tool-specific value.

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 presence of an output schema (not shown), the description covers the key return fields (event names, latency, pricing, schemas, provider env, live status) adequately for a catalog tool. The generic guidance is unnecessary but does not omit critical information about the tool's functionality.

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 single parameter 'pluginId' is fully documented in the schema with a clear example. Schema coverage is 100%, so the description adds no additional value beyond the schema. Baseline 3 is appropriate.

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 it is a stream discovery tool for premium SAP MCP capabilities, listing specific return fields like event names and latency targets. However, it does not explicitly differentiate from sibling catalog tools such as 'sap_premium_plugin_catalog' or 'sap_pricing_catalog', which limits clarity in a rich sibling ecosystem.

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 mentions the tool is 'free' and for 'discovery', implying a low-cost use case, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it state prerequisites or exclusions. The generic SAP execution guidance block does not address usage scenarios specific to this tool.

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