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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds behavioral context beyond the annotations by listing specific return fields (scheduleStatus, watchUrl, launchedAt, isArchived) and indicating that the status can change, making it suitable for polling. No contradiction with annotations.

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 and well-structured: it front-loads the core purpose in the first sentence and adds valuable detail in the second. No redundant information or filler. Every sentence earns its place.

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?

For a simple single-channel getter with one parameter, the description is quite complete. It explains the primary use case, key return fields, and a monitoring pattern via polling. Annotations cover safety, and there's no output schema requiring explanation. It does not mention error behavior for missing channels, but that's a minor gap for this simple 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?

The input schema has a single parameter 'channel_id' with a description 'Channel id', and schema coverage is 100%. The tool description does not add additional meaning for this parameter. Since the schema already fully explains the parameter, a baseline score of 3 is appropriate.

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 function: 'Get one channel by id.' This uses a specific verb (Get), identifies the resource (channel), and specifies the scope (by id). It distinguishes from sibling tools like list_channels by focusing on a single channel retrieval.

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 provides a clear use context: 'poll this to confirm a channel has gone live.' This indicates when to use the tool, though it does not explicitly mention alternatives or exclusions. The polling guidance is a strong usage hint, but it doesn't say 'use list_channels for multiple channels' or similar.

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