offsets__verify_certificate

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

With no annotations provided, the description carries the full burden of disclosure. It states the internal steps (hash recomputation, ledger check) but does not mention failure modes, side effects (likely none), or authentication requirements. Adds basic transparency but not comprehensive.

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 short and includes a domain prefix, but it omits critical details about parameters. It is under-specified rather than efficiently concise, as every sentence should earn its place but does not provide needed information.

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 complexity (nested object parameter, no output schema, no annotations), the description is far from complete. The agent cannot infer the certificate format, return values, or error conditions, making the tool difficult to use correctly.

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 only parameter 'certificate' is an object with no schema descriptions. The description does not specify what properties or structure the certificate should have. With 0% schema coverage, the description fails to compensate, leaving the agent without guidance.

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 the tool verifies an offset certificate by recomputing its hash and checking the ledger. It includes a domain prefix identifying the offsets namespace, and the verb-resource combination distinguishes it from siblings like offsets__book or offsets__buy_offset.

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?

No guidance on when to use this tool versus alternatives (e.g., provenance__verify_certificate) or when not to use it. No context about prerequisites, required permissions, or tool selection criteria.

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