subscribeExecutionFast

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

The description only notes that authentication is required. No details are given about subscription lifecycle, data delivery method (e.g., WebSocket), push frequency, rate limits, or how to stop the subscription. Given the lack of annotations, the description carries the burden of behavioral disclosure but falls short.

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 very short (one sentence), which makes it concise, but it sacrifices important information. It is front-loaded with the core action, but the lack of detail reduces its effectiveness.

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 complexity of a subscription tool with multiple similar siblings, the description is incomplete. It does not explain the subscription mechanism, output format, or how it differs from other subscription tools. The agent would likely struggle to use it correctly without additional context.

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 two parameters (messageCount, timeoutMs) with 0% schema description coverage, and the description does not mention or explain them. The agent receives no guidance on what these parameters control or how to set them appropriately.

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's purpose: subscribing to fast execution push notifications. It also mentions authentication requirement. However, it does not differentiate from similar sibling tools like subscribeExecution, which may have overlapping functionality.

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?

No guidance is provided on when to use this tool versus alternatives. The only prerequisite mentioned is authentication, but there is no context on typical use cases or exclusions.

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