subscribe_bot_metrics

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

Annotations indicate readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds that it fires on every fill, signal, and position update, and uses MCP resource notifications. This provides useful behavior context beyond annotations but does not detail side effects like rate limits or unsubscription methods.

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 two sentences, front-loading the action and event triggers. Every sentence provides value without redundancy. No wasted words.

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 simplicity of the tool (2 required params, no output schema), the description covers purpose, events, and use case. Missing details like return format or unsubscription method, but these are not critical for a basic subscription tool.

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 coverage is 50%: subscriber_id has a description, bot_name does not. The description does not clarify parameters further. However, parameter names are self-explanatory and the tool's purpose implies their roles. A better description would explain bot_name, but the current state is adequate.

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 subscribes to real-time bot metrics via MCP resource notifications, differentiating it from sibling tools that retrieve metrics statically (e.g., get_all_bot_metrics, get_live_bot_metrics). The specific verb 'Subscribe' and resource 'bot metrics stream' make the purpose unambiguous.

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 indicates when to use: for real-time updates on fills, signals, and positions. It mentions 'Perfect for the private bot showcase', providing context. However, it does not explicitly exclude one-time queries or mention alternatives, leaving some ambiguity.

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