provenance__get_certificate

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It merely states the action without clarifying side effects, permissions, rate limits, or whether it is a read operation. The description is minimal and lacks 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 very concise, consisting of a single relevant sentence plus a category prefix in brackets. It is front-loaded and wastes no words. However, it could be slightly more structured or include additional helpful details without becoming verbose.

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?

The tool has no output schema and only one parameter. The description mentions the return value (genesis certificate + recall/quarantine status) but does not elaborate on the format or structure. It is adequate for a simple tool but lacks completeness regarding return data details.

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 the description does not explain the only parameter 'agent_id'. There is no context about its format, expected values, or purpose beyond the schema name. The description fails to compensate for the low coverage.

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 it fetches an agent's genesis certificate and recall/quarantine status, using the specific verb 'Fetch' and identifying the resource ('agent's genesis certificate + recall/quarantine status'). It distinguishes from sibling tools like 'provenance__get_artifact' which fetches a different resource.

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 does not mention prerequisites, when not to use, or suggest sibling tools for related tasks.

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