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

Without annotations, the description carries the full burden. It discloses the output format (trust-weighted quorum answer, confidence, trustedDissent, gate recommendation) and mentions Sybil-resistance and stake-weighting. However, it does not specify side effects (e.g., whether any data is stored) or potential destructive actions, which is acceptable for a likely read/aggregation tool.

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 only two sentences, but the second sentence is dense and technical ('the Sybil-resistant, stake-weighted judge the multi-agent literature prescribes for the 17x error trap'), which may confuse the agent. It could be more concise and clearer without sacrificing key information.

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?

The description explains the output format thoroughly, but it lacks details on error handling, what happens if no consensus is reached, or how trust weights are determined. Given the tool's complexity and no output schema, the description leaves some gaps that an intelligent agent might need.

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 0%, and the description does not explain the three parameters ('task', 'minScore', 'submissions'). It only vaguely references 'agent answers' but fails to clarify the role of 'task' or 'minScore', leaving the agent to infer meaning from context alone.

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 uses active verbs ('submit', 'get') and clearly defines the tool's purpose: aggregating 2-20 agent answers into a single actionable decision with quorum, confidence, dissent, and a gate recommendation. It distinguishes itself from siblings like 'lawbor_quorum' by emphasizing 'turnkey' and specific outputs.

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 implies when to use: when you need a stake-weighted quorum from multiple agents. It mentions the '17x error trap' to indicate suitability for error-prone multi-agent scenarios, but it does not explicitly exclude cases or name disjoint alternatives, leaving some ambiguity.

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