Return the signed Agent Protocol discovery document with public endpoint links, trust surfaces, timestamp, and agent signature.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden for behavioral disclosure. It reveals the signed nature of the document and the main return fields, and 'Return' implies a read-only operation, but it does not discuss authentication, caching, or any other behavioral traits.
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 with no filler. Every clause adds meaningful information about what the tool returns.
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 zero-parameter tool with an output schema, the description covers the key return aspects: signed document, endpoint links, trust surfaces, timestamp, and agent signature. It lacks explicit sibling differentiation and read-only declaration, but the low complexity keeps it largely complete.
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 and an empty input schema, so the baseline is 4. The description adds useful context about the returned content even though parameter semantics are essentially not applicable.
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?
Description uses specific verb 'Return', names the resource 'signed Agent Protocol discovery document', and enumerates its contents ('public endpoint links, trust surfaces, timestamp, agent signature'). This clearly distinguishes it from sibling getters like get_agent_identity or get_attestations.
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?
Usage context is implied by the resource name and description, but no explicit when-to-use or alternatives/exclusions are stated. An agent can infer it is for retrieving the discovery document, but not why it should be chosen over related sibling tools.
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.
Most tools are clearly distinct, targeting specific documents or endpoints (e.g., identity, capabilities, JWKS, receipts). However, some overlap exists among discovery-related tools (e.g., get_agent_discovery, get_agent_identity, get_capabilities, get_marketplace_listing) that could cause confusion about which to use for a given purpose.
All tool names follow a consistent pattern: 'hodlxxi_get_' or 'hodlxxi_verify_' followed by a descriptive noun phrase. The verbs are consistent (get/verify) and the nouns are specific, making the naming predictable and uniform.
With 26 tools, the count is slightly above the typical well-scoped range (3-15) but still reasonable for a read-only server that exposes a wide array of public documents and metadata. Each tool serves a distinct purpose, so the count is justified, though it borders on heavy.
The server covers a comprehensive set of read-only operations for its domain: identity, capabilities, skills, receipts, trust events, OAuth/OIDC metadata, and verification. Minor gaps exist, such as no tool for listing all covenants or reports (only get by identifier), but the core surface is well-covered.