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

Annotations declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds value by specifying the nature of the returned content—conflict points, opposing stances, dissenting opinions, alternative proposals—but does not disclose behaviors like ordering, aggregation, or handling of empty results. With annotations present, a 3 is appropriate.

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 a single, compact sentence that front-loads the core concept ('Main points of conflict') and then elaborates with illustrative examples. It contains no filler and earns its length, though it could be slightly more explicit with a leading verb.

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 retrieval with a single well-documented parameter and no output schema, the description adequately conveys what the tool returns. It gives enough detail about the nature of the results that an agent can decide whether this tool matches the user's intent. Minor gaps like result formatting or edge-case behavior are acceptable given the tool's simplicity.

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 input schema already documents thread_id with a description ('Discussion (thread) id'), giving 100% schema coverage. The description adds no parameter-specific semantics beyond what the schema provides, so the baseline of 3 applies. No additional context is needed for this single, well-documented parameter.

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 identifies the resource as 'main points of conflict' and elaborates with concrete examples: exchanges between opposing stances, dissenting opinions, and alternative proposals. Though it lacks an explicit verb, the tool name and title supply 'get', making the action unambiguous. It differentiates from siblings like get_consensus and get_argument_map by focusing on conflict points.

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 guidance on when to use this tool versus alternatives such as get_consensus or get_argument_map. The description simply defines the output without any contextual cues about typical use cases, prerequisites, or exclusions. An agent would have to infer usage from the name alone.

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