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

Goes well beyond the read-only/idempotent annotations: it defines the returned fields (seals, complete, counted_through_ts), explains what 'complete' means for the count's finality, and explicitly says POAScan never decodes or publishes a sealed grade or pending score. That privacy/decoding constraint is exactly the kind of behavioral context annotations cannot express.

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-loads the core purpose and keeps all sentences substantive, with no filler. The first sentence is long and parenthetical-heavy, which slightly hurts readability, 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 supplies the semantics of all three returned fields and the boundary of what the tool will reveal. For a single-parameter read tool this is complete: an agent knows what it gets, how final the count is, and where to go for settlement state.

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% and the txid parameter's 64-hex format is documented in the schema. The description only implies that the txid identifies the answer/challenge tx, adding marginal meaning beyond the schema; 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: counts grade seal txs that name one answer (challenge) tx. It also names the sibling get_answer_receipt and explains the different question that sibling answers, so an agent can distinguish the two without opening either schema.

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?

Explicitly gives the use case ('see whether an answer is being graded') and names the alternative for a related question ('for the settle state use get_answer_receipt'). The routing rule between this and the settle-state tool is unambiguous.

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