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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds useful content-level context by naming what is included (timeline, construction sequence, chain identity, tokenization) and the specific edge types (cut_from, placed_as, pinned_as, pictured_by, hash_of). It does not describe permissions, cost, or the shape/format of the response.

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?

It is a single sentence with no filler, but it is a dense comma-separated dump of return categories with no front-loaded action or guidance. The reader must parse a long list to infer what the tool actually does.

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?

There is no output schema, so the description bears responsibility for conveying return content — and it does enumerate the categories and relationship types reasonably well. However, it gives no usage routing against the overlapping evidence/proof siblings and no sense of response structure, leaving the definition only minimally adequate.

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 100% and the single asset_id parameter is fully documented with accepted formats (PT-0001, RUTHVEN-PT-0000001, work number). The description says nothing about the parameter, so it adds no value beyond the schema; the baseline of 3 applies when the schema does all the work.

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 opening phrase 'Provenance and lineage' names the resource clearly, but the description is essentially an inventory of returned data rather than a statement of what the tool does — there is no verb (fetch/return/compute). It also fails to distinguish itself from close siblings like ruthven_get_evidence or ruthven_get_proof, which overlap with the 'evidence graph' it claims to return.

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 when-to-use guidance, no prerequisites, and no named alternatives. With siblings such as ruthven_get_evidence, ruthven_get_proof, and ruthven_get_asset in the same family, the agent gets no signal for choosing this tool over those.

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