healthCheck the governance gateway health status. Free.
| Name | Required | Description | Default |
|---|---|---|---|
| verbose | No | Return additional details such as chain length and PQC signing status |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds 'Free' as a behavioral trait (no cost) and clarifies the target scope, but does not provide deeper details like response structure or side effects beyond what annotations offer.
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: two short sentences. Every word earns its place, with 'Free' conveying a useful behavioral note without unnecessary elaboration.
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?
For a simple health-check tool with one optional parameter and an output schema, the description is reasonably complete. Annotations cover safety, the schema covers parameters, and the output schema covers return values. However, the lack of usage guidance and sibling differentiation prevents a perfect score.
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 single parameter 'verbose' is fully described in the schema with its default and purpose. The tool description does not add parameter-level meaning, but since schema coverage is 100%, the baseline of 3 is appropriate.
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 action ('Check') and the resource ('governance gateway health status'), making the tool's purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'status' or 'check-peer', so it lacks explicit sibling distinction.
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. The description mentions it is 'Free' but does not explain scenarios where a health check is preferred over other governance gateway tools, nor any prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action or resource: attest creates provenance records, bind declares intent, bundle aggregates evidence, verify checks policy pre-execution, verify-outcome validates results, and verify-token authenticates release tokens. Even the verify-* family is clearly differentiated by timing and purpose.
Tool names consistently use lowercase imperative verbs, with hyphenated modifiers for multi-word names (check-peer, verify-outcome, verify-token). The pattern is mostly consistent, though some tools are bare verbs (attest, bind, health) while others include a noun, creating a minor deviation from strict verb_noun style.
Nine tools is well within the ideal range for this domain. Each tool serves a clear purpose in the agentic identity trust lifecycle, from evidence creation to verification and peer assessment, without redundancy or excessive sprawl.
The tool surface covers the core workflow: intent binding, policy verification, provenance attestation, outcome verification, token verification, and compliance bundling. Minor gaps exist such as missing explicit revocation or role management, but agents can complete the primary governance lifecycle.