provenance__register_genesis

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

Discloses key behaviors: content-addressed certificate, monotone index, epoch 0, lineage tracking, quarantine effect, idempotency. No annotation contradiction.

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?

Two sentences plus a domain prefix; every sentence adds value without redundancy. Front-loaded with purpose.

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?

Adequately covers behavior and constraints for a 3-parameter tool with no output schema. Minor gap: missing artifact_hash explanation and output description.

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 coverage is 0% so description must compensate. It explains agent_id and parent_id well, but does not mention artifact_hash parameter at all.

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?

Clearly states the tool registers an agent's birth, issues a genesis certificate, and handles lineage. Distinguishes from sibling tools by focusing on birth/genesis.

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 when to use (for agent registration) with constraints like idempotency and quarantine on recalled parents, but no explicit alternatives or when-not-to-use guidance.

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