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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds the verdict taxonomy (matches, differs, disputed, unknown) and which extra fields accompany them, plus a real limitation: it compares values and does not judge meaning. That is valuable context annotations cannot supply; it stops short of saying how comparison normalizes whitespace/case or whether missing cells error.

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?

Front-loaded with the action, then the verdict semantics, then the caveat, then the prerequisite. Every sentence carries information, though the parenthetical asides ('so say so', 'with what the source states') make it slightly denser than needed.

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?

With no output schema, the description carries the burden of explaining return values and does so via the four verdicts and the `conflicts` reference. The remaining gap is comparison rules (normalization, what `differs` quotes look like) for a tool whose entire purpose is value comparison.

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 coverage is 100%, with each parameter documented inline including its provenance (row from get_table, slug from list_tables). The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource — 'Test a statement against one cell' — and illustrates with a concrete scenario (a draft or an answer). It implicitly separates itself from the read-only sibling get_cell and from fill_cells, though it never explicitly contrasts with 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?

Gives a clear prerequisite workflow: 'Use list_tables and get_table to find the cell first', and cautions to 'read the quote before relying on a text verdict'. It does not name an alternative tool to use instead when the agent only wants to read a value (get_cell).

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