notary__verify

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

Describes verification but does not disclose side-effects, idempotency, or permissions. No annotations provided to compensate. Adds some context about delivery proofs.

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 concise sentence with context prefix. Slightly redundant 'commit-reveal' but efficient overall.

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?

Covers core functionality and parameter roles but lacks return value description, error cases, and prerequisites. Schema description coverage is 0% so description compensates partially.

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?

Explains commitment_id as the commitment to verify and content_digest as optional check. Adds meaning beyond schema fields which have no descriptions.

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?

Clearly states it verifies a revealed commitment and optionally checks against a content digest. Distinguishes from sibling notary tools like commit, reveal, status.

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?

Suggests use after a reveal and for checking content, but lacks explicit guidance on when not to use or alternatives. Siblings include commitment_status which might overlap.

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