provenance__get_certificate

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

No annotations provided, so description carries full burden. Indicates a read operation, but omits details like error handling, permission requirements, or what 'recall/quarantine status' specifically includes. Adequate but minimal.

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?

Single sentence, front-loaded with domain context, concise with no wasted words.

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 one required parameter, no output schema, and siblings, the description is minimally viable but lacks details on output structure and retrieval conditions, which could confuse agents unfamiliar with the domain.

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?

Schema description coverage is 0%, and description adds no extra meaning beyond the parameter name 'agent_id'. The phrase 'an agent's genesis certificate' implies the agent_id, but does not clarify format, constraints, or required relationships.

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 explicitly states it fetches an agent's genesis certificate and recall/quarantine status, using specific verb 'fetch' and resource. Clearly distinguishes from sibling tools like get_artifact, recall, or verify_certificate.

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?

Implies usage when needing genesis certificate or recall status, but lacks explicit when-not or alternative guidance. For example, no distinction from verify_certificate or lineage.

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