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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds a genuine behavioral detail beyond that: it 'looks for opinion/debate signals in titles' and implies returned items are pairs ('max debate pairs'), which aids an agent in anticipating results and methodology. No contradictions.

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?

Two sentences only, tightly written. The core function is front-loaded, the scoping detail about title signals comes second, and the usage examples close it out. Every clause adds value with no repetition or filler.

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?

Given that this is a simple read-only tool with one optional, fully documented parameter and no output schema, the description covers what it does, how it does it, and when to call it. The only minor gap is that the exact shape of a 'pair' is not specified, but this does not block correct invocation.

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 100%: the 'limit' parameter is already fully described as 'Max debate pairs to return (default: 8, max: 15)'. The description does not add any additional semantic info about the parameter, so the baseline of 3 is appropriate.

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 states a specific verb+resource ('Find posts on similar topics that may argue different sides') and names the differentiated output ('surfaces contrasting viewpoints'). The phrases 'opposing viewpoints' and 'where do my saves disagree?' help distinguish it from sibling tools like find_similar_posts (which presumably finds similar perspectives) without even naming them.

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 provides clear, concrete use cases: 'find debates in my saves', 'opposing viewpoints', 'where do my saves disagree?'. This frames when to invoke the tool, but it does not name alternative tools or state when not to use it, so it stops short of full when/when-not guidance.

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