get_reputation_attestation_contractReturn the portable attestation, trust-profile, verifier-result, endpoint-registry, and lifecycle contracts.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate idempotent, read-only, non-destructive behavior. The description adds that it returns a specific set of contracts, which is useful beyond annotations.
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 clear sentence, front-loading the key information. Slight improvement possible with more structure, but effective.
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 no parameters and no output schema, the description adequately specifies what is returned. It is complete for a simple retrieval tool.
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?
No parameters exist, and schema coverage is 100%. The description does not need to add parameter info, and the baseline is 4.
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 returns specific contracts (portable attestation, trust-profile, verifier-result, endpoint-registry, lifecycle contracts), distinguishing it from siblings like 'discover_afmr' and 'lookup_failure_mode'.
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 explicit guidance on when to use this tool versus alternatives. While the purpose is clear, the description lacks context about prerequisites or scenarios where this tool is preferred.
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 has a clearly distinct purpose: one returns canonical AFMR specs, two return specific contracts (lift evidence and reputation attestation), and one looks up failure modes. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case: discover_afmr, get_lift_evidence_contract, get_reputation_attestation_contract, lookup_failure_mode. No deviations or mixed conventions.
Four tools are well-scoped for a discovery service. Each tool earns its place, covering key functions without being too few or too many.
The tool set covers the main aspects of AFMR discovery: general specs, two key contracts, and failure mode lookup. There are no obvious gaps for the stated domain.