telemetry_subscribe

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

Discloses blocking nature ('blocks and streams inline progress'), behavior with/without jobId, and timeout limit. With no annotations, description adequately conveys the streaming and blocking 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?

Single sentence efficiently packs purpose, blocking behavior, conditional logic, and timeout. Could be slightly more structured but 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?

Explains core behavior but lacks details on event format, stop mechanisms beyond timeout, or output expectations. Without output schema, more context on return format would be helpful.

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 already covers both parameters well (100% coverage). Description adds minimal new meaning beyond 'omit to watch next job' which is redundant with schema.

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?

Clearly states 'Watch live job events as they happen' with specific verb and resource. Distinguishes from siblings telemetry_jobs (list) and telemetry_job_status (status check) by focusing on real-time streaming.

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?

Implies use for live monitoring but does not explicitly state when to use vs alternatives like telemetry_job_status for one-time checks. No when-not-to-use guidance.

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