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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful semantic context beyond those hints by labeling the data 'provisional' and emphasizing it is 'diagnostic information, not a binding outcome,' which helps an agent understand that the results should not be treated as final decisions.

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 at two sentences with no filler. The first sentence front-loads the action, target data, and scope; the second sentence reinforces the diagnostic nature. Every clause earns its place.

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 tool with one optional parameter, rich annotations, and no output schema, the description provides enough to invoke it correctly: it names the data categories read, explains the target scope, and clarifies the diagnostic intent. Nothing critical is missing for an agent to decide and call the tool.

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?

With only one optional parameter and 100% schema description coverage, the schema already explains 'Optional debate identifier. Omit to inspect all open debates.' The description's phrase 'for one or all open debates' essentially mirrors the schema, so it adds no substantive parameter meaning beyond what is already structured.

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 opens with a specific verb ('Read') and a specific resource: 'provisional genesis date floor, qualified-agent threshold and transparent diversity indicators.' It also clarifies scope ('for one or all open debates'), which clearly distinguishes it from siblings like list_debates or hot_debates.

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 context for when the tool is appropriate: it is for inspecting diagnostic readiness information, and the closing statement 'not a binding outcome' sets expectations that this is informational rather than authoritative. It does not explicitly name alternative tools, but the 'for one or all open debates' scope plus the diagnostic framing provide sufficient guidance.

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