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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds 'deterministic signed,' which hints at a reproducibility and output-signing property, but it does not clarify what 'signed' means here or what side effects, if any, the assessment has on the supplied input.

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 short and front-loaded, with no wasted phrasing. However, it is terse to the point of under-specification, leaving important semantic and selection information absent.

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 large, semantically overlapping sibling list and unnamed required parameters, the description is incomplete for reliable tool selection and invocation. The presence of an output schema helps, but the description still fails to convey the intended use case, input semantics, or differentiation criteria.

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 required parameters 'memory' and 'source' are given no semantic explanation in either the schema or the description. The phrase 'supplied input' is generic and does not clarify which parameter maps to which concept, so an agent cannot confidently determine what values to provide.

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 says the tool produces a 'deterministic signed assessment over supplied input,' which conveys the basic operation and resource. However, it does not explain what 'agent memory provenance' means, what question is being answered, or how this differs from many similarly named provenance/attestation siblings.

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?

There is no guidance about when to use this tool versus alternatives. The sibling list contains numerous provenance, evidence, and attestation tools, but the description provides no conditions, prerequisites, or exclusions to help an agent choose among them.

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