provenance__list_records

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

No annotations are provided, so the description bears the full burden. It only states the basic operation and epoch filter, with no mention of behavioral traits such as side effects, pagination, ordering, or result format. Given the lack of annotations, more detail is expected.

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 sentence that front-loads the purpose. It includes a helpful prefix for context and no extraneous information. Every word adds value.

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 the simplicity (one optional parameter, no output schema), the description is minimally adequate. However, it omits details about the return format or any pagination/limiting behavior, which would be helpful for an agent invoking this 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?

The only parameter 'epoch' has no description in the schema (0% coverage), but the tool description adds meaningful context: 'optionally by epoch (0 = founding cohort)'. This clarifies the meaning of epoch values beyond the raw schema type.

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 verb 'List', the resource 'genesis records', and the optional filter by epoch. The prefix '[provenance — genesis certificates, lineage, recalls]' provides domain context and differentiates from sibling tools such as provenance__list_artifacts or provenance__get_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?

The description implies usage for listing genesis records with an optional epoch filter, but does not explicitly state when to use this tool versus alternatives like provenance__list_artifacts. No exclusions or context for when not to use it are provided.

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