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

Annotations already declare a non-read-only, non-destructive, open-world mutation, and the description adds that muted:true suppresses the notification stream. It does not clarify permission requirements, duplicate-subscription behavior, or notification defaults, so it adds useful but limited behavioral context.

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?

Two sentences, front-loaded with the action and valid targets, then the muted behavior. There is no filler or repetition.

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 mutation with nested input, an idempotency key, and no output schema, the description covers the core action and muted flag but leaves access requirements and idempotency behavior to annotations/schema. It is minimally adequate but not fully complete.

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 description adds meaning beyond the schema by explaining that target_id can be an area or an accessible discussion and by defining the effect of muted. With only 50% schema description coverage, this is helpful, but idempotency_key semantics and some target constraints remain delegated to the 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?

The description states a specific verb, “Subscribe,” and identifies valid resources: the listed area targets or one accessible discussion. It is clearly distinguishable from collaboration_unsubscribe by its subscribe action, though it does not explicitly contrast itself with sibling subscription-listing tools.

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 implies when to use the tool by listing acceptable subscription targets and explaining the muted option. However, it gives no explicit guidance on when to choose this over collaboration_unsubscribe or collaboration_subscriptions, nor any prerequisites beyond “accessible.”

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