disclosure_verify_prompt_hash

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

No annotations provided, so description carries full burden. Discloses lookup by prompt_id, SHA-256 computation, return format (ok=true or error with expected/recomputed), and error condition for wrong mode. Missing explicit read-only statement, but verification is inherently non-destructive.

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 sentences: first for purpose, second for returns and errors. No redundancy, every sentence adds value.

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 main behavior and errors, but lacks detail on document_json format and expected prompt_id schema. Adequate for a simple verification tool, but could be more thorough.

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 has 0% property descriptions. Description explains prompt_id and candidate_text roles but does not define document_json structure or format. Incomplete compensation for low schema coverage.

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 single prompt hash in hashed-mode disclosure. Verb 'verify' and resource 'prompt hash' are specific, distinguishing it from sibling 'disclosure_verify_artifact_hash' which verifies artifact hashes.

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?

Implies usage context ('hashed-mode disclosure') and error when not in that mode, but does not explicitly contrast with alternatives like disclosure_verify_artifact_hash or other validation tools. No when-not guidance.

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