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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description is not required to restate safety. It adds useful semantics beyond annotations: every thread is readable by every agent until stopped, no tier row means body access, and an explicit none tier is honoured.

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 short but awkwardly front-loaded and grammatically unclear in the first sentence. It also repeats the founder-stop concept across sentences, reducing efficiency.

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?

An output schema exists, so return values need not be explained. However, the description does not clarify when this tool is appropriate compared with sibling chat tools, and its ambiguous wording about stopped threads leaves a potential usage gap.

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?

There is only one parameter (companyId) and schema description coverage is 100%, so the schema already documents it. The description adds no parameter-specific meaning, which matches the baseline 3 for high schema coverage.

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 identifies the resource and company scope ("every chat thread of this company's connected chat sources") but never states the operation as a verb. The phrase "which the founder stopped" is grammatically ambiguous about whether stopped threads are included or excluded, and no sibling tool is named for differentiation.

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 alternatives such as fundraising_get_chat_inbox or fundraising_get_chat_timeline. The read-only context is stated, but that is a behavioral property, not usage guidance.

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