subscribeSpreadExecution

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

The annotations already provide readOnlyHint=true and openWorldHint=true, so the basic safety profile is covered. The description adds the useful context that this is a push subscription requiring authentication, but it does not explain the subscription lifecycle, how messages are returned, or how timeoutMs and messageCount affect behavior.

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 concise sentence with the core action and resource front-loaded, and the auth requirement is a useful parenthetical. It is appropriately short for the simplicity of the tool, though it omits parameter and alternative-selection context.

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?

With no output schema and many sibling subscription tools, the description is not complete enough for an agent to reliably select and invoke this tool. It fails to clarify the difference from general execution subscriptions, public spread trade subscriptions, or how the subscription result is delivered.

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%, and the description gives no explanation of timeoutMs or messageCount. The parameter names and defaults are somewhat self-explanatory, but the description does not clarify whether the tool blocks until messageCount messages arrive, how timeout interacts with the count, or what the delivered messages contain.

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 states a specific verb and resource: subscribing to Spread execution push notifications. It also mentions that authentication is required, which importantly signals this is private data, but it does not explicitly distinguish itself from sibling tools such as subscribeSpreadOrder, subscribeSpreadPublicTrade, or subscribeExecution.

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 only usage guidance is that authentication is required. There is no statement about when to use this tool instead of subscribeExecution, subscribeExecutionFast, subscribeSpreadOrder, or subscribeSpreadPublicTrade, so an agent must infer the appropriate choice from the name alone.

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