trust__verify_attestation

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

No annotations provided, so description must disclose behavior. It only states the verification method (recompute hash) but does not mention side effects, auth requirements, rate limits, or whether it is read-only. Minimal transparency.

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?

The description is extremely concise—a single sentence plus a domain prefix. It wastes no words but could benefit from more structure (e.g., separating purpose from method).

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?

Given no output schema and no annotations, the description leaves out crucial context: what the verification result looks like, expected format, or any prerequisites. Incomplete for confident tool invocation.

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 description coverage is 0% and the description adds no meaning to agent_id or attestation_id beyond their names. With no parameter elaboration, the description fails to aid correct parameter usage.

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 clearly states 'Verify a previously issued attestation by recomputing its hash,' specifying the action (verify), resource (attestation), and method (recompute hash). The bracketed prefix provides domain context distinguishing it from sibling tools like trust__attest.

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 description implies when to use (to verify an attestation) but lacks explicit guidance on when not to use or alternatives. No mention of prerequisites or comparison to related tools like notary__verify.

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