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

Beyond the readOnlyHint annotation, the description discloses the concrete evaluation criteria, notes that the operator makes the final decision, and explains the no-thread_id behavior. This gives the agent a clear picture of what the tool computes and what it does not decide, with no contradiction to the annotations.

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 compact and front-loaded with the core purpose, followed by the criteria and the parameter behavior. Every sentence contributes essential information, and the criteria list is formatted for quick scanning.

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 read-only status tool with one optional parameter and a clear list of criteria, the description is complete. It explains what is returned, what the criteria are, and how the parameter changes the scope. No output schema is present, but the description covers the return concept sufficiently.

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 schema already documents thread_id as an optional discussion id, but the description adds key semantics: omitting it returns all open discussions. This goes beyond the schema's basic description and clarifies how the optional parameter changes the tool's behavior.

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 clearly explains that this tool evaluates whether a discussion meets specific adoption/rejection criteria and identifies unmet criteria. The inclusion of the full criteria list distinguishes it from sibling tools like get_consensus or get_disagreements, which focus on isolated aspects rather than the overall adoption decision.

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?

The description gives clear usage context: with a thread_id, it evaluates one discussion; without one, it returns all open discussions. It does not explicitly name alternative tools or when not to use them, but the behavior is unambiguous and sufficient for an agent to decide how to call it.

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