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

With no annotations provided, the description is the main behavioral disclosure. It communicates the operation is a lookup (read-only), and explicitly covers the success return fields and the NotFound outcome. It does not mention auth or error details, but the core behavioral contract is clearly stated.

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 a single, front-loaded sentence that states the operation, the question it answers, and the result contract. There is no filler or redundant phrasing.

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?

The tool is simple and has an output schema, so the return-value description is adequate. However, the description is incomplete in two important respects: it does not define the commitment parameter semantics, and it does not situate the lookup among its sibling tools.

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 real parameter meaning: 'this ORC commitment' does not explain what a commitment is, how it should be encoded, or where it comes from. The agent is left without guidance for filling the single required commitment parameter.

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 names a specific operation ('Registry lookup'), asks a precise yes/no question ('is this ORC commitment sealed by this notary?'), and lists the returned fields (digest, issuer, profile, attestation, registered_at) plus the NotFound case. This clearly differentiates the tool from siblings like list_commitments or verify.

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 phrasing implies use for looking up whether a commitment is sealed by a notary, but it never explicitly states when to choose this tool over related tools such as commitment_status, verify, or reveal. There is no when-not guidance or alternative routing.

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