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

The description states deterministic, evidence-bounded, and signed, which adds behavioral context, but it contradicts the annotations: it describes a committing action that likely creates a new proof, yet readOnlyHint is true. This is a clear contradiction that undermines trust.

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 and front-loaded with the core purpose, but it sacrifices clarity for brevity. Every word is purposeful, yet the vagueness reduces its effectiveness. Still, it's a single sentence that is easy to scan.

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 the tool has an output schema, the return value may be covered, but the description provides no details on the input format, the types of evidence accepted, or the exact semantics of 'commit'. The contradiction with annotations and lack of usage guidelines make it incomplete for reliable 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?

The tool has zero parameters, so the description doesn't need to explain any. The schema is open to any properties, but with no fixed parameters, the baseline for parameter semantics is high.

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 uses the verb 'Commit' and names a specific resource ('request, authority, execution, payment and delivery evidence'), but it is vague about what the tool actually does—it sounds like a wrapper that bundles several evidence types into one proof, yet the exact operation and output are unclear. It does not distinguish itself from siblings like 'delivery_evidence' or 'fetch_evidence'.

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 provides no explicit guidance on when to use this tool versus alternatives. It mentions a cost and determinism, but not the conditions under which this should be chosen over similar evidence tools. Agents are left to infer use cases.

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