Countersign

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

With no annotations, the description carries the full burden. It does disclose that this is a read of a public log, that results are ordered from newest after a cursor, and that the head hash and public key are returned — real behavioral value. It omits auth/rate-limit behavior, whether the head fields describe the log tip or something else, and any response shape detail.

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?

One front-loaded sentence with no filler. Slightly compressed to the point of ambiguity — "its head hash and public key" leaves unclear whether these describe the log head or the newest entry.

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?

A cryptographic log tool with no annotations, no output schema, and no parameter documentation needs more than one sentence. The return payload (entries, head hash, public key) is only gestured at, and nothing explains what the head hash is for or how it relates to countersign_verify.

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 0% with two parameters, so the description must compensate. "Newest after a sequence number" successfully explains the semantics of `after` as a forward cursor, but `limit` is never mentioned or bounded, leaving half the parameters undocumented.

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?

"Read the public stamp log" gives a clear verb (read) and resource (stamp log), and adds that the response includes head hash and public key. It does not explicitly distinguish itself from countersign_verify or countersign_stamp, but the read-only framing makes the split inferable.

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?

No when-to-use guidance and no named alternative. The phrase "newest after a sequence number" hints at incremental polling, but nothing tells the agent whether to use this versus countersign_verify when it needs to check a stamp's validity.

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

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

There are no annotations, so the description carries the full burden, and it discloses a lot about the behavior: the verification methods used, the three-valued outcome, that findings include time and method, and that stamps are published in a public log. The public-log exposure is an important side effect to disclose, and it does so. It omits operational traits such as permissions, latency/cost, or failure modes, which keeps it from a 5.

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?

Three sentences, front-loaded with the 'Use when' trigger, then the mechanism, then the output. Every sentence carries information and none is redundant. It is dense but not bloated.

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 7 parameters, nested objects, and no output schema, the description does the necessary work of describing the return value (a signed stamp with pass/fail/inconclusive plus findings, time, and method). It also flags the public-log side effect that the private parameter mitigates. Minor gaps remain around error conditions and the exact independence rule mechanics, but an agent has enough to call it correctly.

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 already 86% and each property explains itself, so the schema baseline of 3 applies. The description adds useful framing by connecting the checkable artifact types to the verification actions (arithmetic re-computation, quoting and value lookup, link opening, code parsing) that map onto kind, claims, sources, and language. It says nothing specific about producer or the independence rule's mechanics beyond naming it.

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 states a specific verb and resource: an independent, signed check of a piece of work (report, calculation, summary, filing draft, code) that returns a pass/fail/inconclusive stamp. The scope of the check (re-computing arithmetic, verifying quotes and values against cited sources, opening links, parsing code) further pins it down. It never explicitly names the siblings countersign_log and countersign_verify, so an agent gets no direct disambiguation between the three.

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?

'Use when you need an independent, signed check of work you or another agent produced ... before relying on it or handing it on' is an explicit trigger condition. The exclusion 'It never checks work it produced' sets a clear boundary on applicability, which is effectively a when-not rule. However, it gives no guidance on when to prefer this over countersign_log or countersign_verify.

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

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

No annotations are provided, so the description carries the full burden. It does disclose the two things returned (public-log membership, hash/signature validity) and implies a read-only operation, but says nothing about error behavior for unknown ids, network/log dependency, or whether a negative result is an error or a false value.

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?

Two tightly written sentences: the action and its required argument are front-loaded, followed by the optional argument and the return semantics. No filler or repetition.

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 and no annotations, the description does roughly the right amount of work: it names both inputs and summarizes the two verification results. It stops short of describing the response shape (booleans vs. status object) and the failure mode, which leaves a small but real gap.

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 0%, so the description must supply meaning: it explains the required id and the purpose of the optional text argument ('the work ... exactly that text'). However, it never uses the actual schema name 'output', so an agent must infer that 'the work' maps to the 'output' property, and no format constraints are given.

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 ('Confirm a Countersign stamp is real') and makes clear this is verification rather than stamping or listing, which separates it from countersign_stamp and countersign_log 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?

The optional second argument's purpose ('to confirm the stamp is for exactly that text') implies when to supply it, but the description never explicitly says when to use this tool versus countersign_log or countersign_stamp, nor what to do when verification fails.

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