subscribeSpreadExecution

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

With no annotations, the description carries full burden. It discloses authentication need but fails to explain subscription behavior: whether it's continuous, how to stop, what triggers pushes, or timeout implications. Key behavioral traits are missing.

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 concise (single phrase) but lacks structure and necessary details. Front-loading purpose is good, but brevity comes at the cost of completeness.

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 (subscription with two parameters, no output schema, many similar siblings), the description is incomplete. It does not explain how the subscription works, how to stop it, or differentiate from other subscription tools.

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 does not mention the parameters (messageCount, timeoutMs) at all. It adds no meaning beyond the schema, leaving the agent to infer their role in the subscription context.

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 tool subscribes to Spread execution push and requires authentication. The verb 'subscribe' and resource 'spread execution push' are specific and distinguish it from sibling tools like subscribeExecution or subscribeSpreadOrder.

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 authentication requirement but provides no guidance on when to use this tool vs other subscription tools (e.g., subscribeExecution, subscribeSpreadOrder). No explicit when-not or alternative recommendations.

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