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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description still adds real behavioral substance: what `absent` means (source was read and yields no such value), what `confirmed` implies about second-reader backing, and how `conflicts`, `history`, and `watch` behave — context the annotations cannot convey.

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?

Purpose is front-loaded in the first clause, then each subsequent sentence documents one return field with no filler. The run-on density and backtick-heavy field listing make it slightly hard to scan, but nothing is wasted.

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 usefully explains the shape of the returned evidence (source, quote, url, confirmed, conflicts, history, watch), and the input side is fully covered by the schema. What is missing is the relationship to sibling read tools and any pagination or error behavior.

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?

All three parameters (slug, row, column) carry 100% schema descriptions pointing at list_tables/get_table for their values, so the schema does the heavy lifting. The description adds no interpretation of slug, row, or column, so the baseline of 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?

The description makes clear this returns the evidence/provenance for a single cell value (source, quote, source type, read time), which is a specific resource. It never names a verb like 'get' or 'fetch' and never contrasts itself with get_table or check_claim, so an agent gets the what but not the boundary.

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?

Usage is only implied: the mention of missing values, `absent`, `conflicts`, and `history` hints this is the tool for verifying or auditing a single cell. There is no explicit 'use this when…' and no routing away from siblings such as get_table (whole-table read) or check_claim (claim verification).

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