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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral context by mentioning mute state, resumability, and that no notification delivery is implied, but it does not explain pagination behavior, return shape, or mute semantics in detail.

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 definition is short and front-loads the resource and scope. The second sentence is somewhat awkward and ambiguous, but it is not wasted length and adds a caveat about notification delivery.

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 read-only listing tool, the annotations already cover safety and the description gives enough to identify the resource. However, with no output schema and 0% schema description coverage, an agent is left without concrete details about pagination parameters and what the returned subscription entries contain.

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 0%, so the description must compensate for two undocumented parameters. It only hints at resumability, which loosely implies that cursor exists, but says nothing about what limit controls, valid ranges, or how cursor values should be passed.

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 title 'Read your subscriptions' supplies the verb, while the description names the resource and scope: the caller's own area/thread subscriptions, including mute state. This distinguishes it from sibling mutation tools like collaboration_subscribe and collaboration_unsubscribe, though the description itself uses the vague verb 'Own' rather than an explicit read/list verb.

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?

There is no explicit guidance on when to use this tool versus collaboration_subscribe, collaboration_unsubscribe, or collaboration_thread. The 'No notification delivery' sentence is a caveat rather than a usage condition, so an agent must infer the appropriate context.

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