offsets__verify_certificate

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

The description discloses that verification involves hash recomputation and ledger checking, implying a read operation with no side effects. However, it omits details such as permission requirements, error handling, or what happens if the certificate is invalid. With no annotations, the description provides moderate 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 a single sentence, which is concise but lacks structural elements like examples or required fields. It is front-loaded but overly brief given the complexity of the parameter.

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 (one nested object parameter, no output schema), the description is incomplete. It does not explain the certificate's required properties, expected output, or potential errors. The agent would need additional context to use this tool effectively.

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 sole parameter 'certificate' is an arbitrary object with additionalProperties: true, and the description does not clarify its expected structure. With 0% schema description coverage, the tool description adds no meaning beyond the raw schema, leaving the agent without guidance on how to construct valid input.

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 uses a specific verb ('Verify') and resource ('offset certificate'), and the action is distinct from siblings like 'verify_disbursement' and 'verify_retirement'.

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 is provided on when to use this tool versus alternatives like 'green-router__verify_green_certificate' or 'provenance__verify_certificate'. There is no mention of prerequisites, exclusions, or typical use cases.

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