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

With no annotations, the description carries the full behavioral burden. It discloses the authorization prerequisite (owner-only), the state change (freeze), and precise consequences on related calls: host.channel.post returns channel_frozen while host.channel.read keeps working. This is strong, concrete behavioral disclosure.

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 tight sentences: the first front-loads the operation and owner restriction, the second packs the key side effects into a compact, semicolon-joined clause. There is no filler or repetition of schema content.

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 2-parameter mutation with no output schema, the description gives enough selection and side-effect context for a correct call. It omits the reversal path (host.channel.unfreeze) and response/error details, but neither is required for basic invocation.

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 100%, so the schema already documents channel_id and tenant_key. The description adds no further param-specific semantics beyond referring to 'a group channel', which is consistent with the schema but not additive.

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 uses a specific verb and resource ('freeze a group channel') and sharpens scope with 'Owner-only'. It differentiates itself from siblings by specifying the effect on host.channel.post and host.channel.read, making the tool's 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?

It clearly states when the tool is appropriate: owner-only action on a group channel, with the consequence that posts are blocked but reads still work. It does not explicitly name alternatives like host.channel.unfreeze or host.channel.close, but the context is clear enough for an agent to decide correctly.

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