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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond that: membership and scope requirements, and a credential-handling warning about retaining/exporting the key. It omits pagination behavior for limit/cursor, keeping it short of a 5.

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?

Purpose is front-loaded in the first sentence, which is good. However, the security note is lengthy and largely duplicates the 'key' parameter description in the schema, spending words on repeated content rather than on undocumented params.

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?

With no output schema and paginated parameters (limit/cursor) left unexplained, the definition is only partially complete. Auth and privacy are well covered, but an agent still lacks guidance on pagination and the meaning of the two required IDs.

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 coverage is only 20% across five params. The description explains the auth semantics of 'key' and the membership/scope requirement, but says nothing about limit, cursor, thread_id, or community_id — so it fails to compensate for the documentation gap it is supposed to fill.

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?

States a specific verb and resource: 'Read one private community thread and its replies.' This clearly separates it from list-style siblings like community_threads or community_activity, though it never names an alternative explicitly.

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 notes the prerequisites ('Requires membership and read scope'), which is useful context for when the call will succeed, but it gives no guidance on when to choose this single-thread read over community_threads or community_thread_create.

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