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

Annotations already mark the tool as readOnly, and the description adds substantial behavioral detail beyond that: snapshots persist at mutation boundaries, old versions are filtered but stored, hidden_count explains empty results, and pinned versions bypass retention. No contradiction with annotations exists.

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 long but dense and front-loaded. Every sentence adds operational meaning, such as revision_id stability, hidden_count semantics, and pinned-version behavior. Given the absence of an output schema, the included return-shape summary is necessary rather than redundant.

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?

Since there is no output schema, the description provides the full return shape, retention-window behavior, pin-cap semantics, and ordering ('newest first'). It also clarifies model_id handling for key scopes. The tool is complex, and the description covers the call-relevant details well.

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%, so the schema already documents limit, since, and model_id. The description mostly restates that since or limit can scope the response, adding little parameter-specific meaning beyond what the schema provides.

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 states a specific verb and resource: 'List the most-recent change history (versions) for a model.' It also defines what a version is and clarifies the relationship to sibling tools like layerz_diff and layerz_pin_version, making the tool's role easy to distinguish.

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 gives clear usage context: the returned revision_id can be used with layerz_diff or to detect concurrent writes, and since/limit can scope the response. It does not explicitly say when to choose this tool instead of layerz_history_for_item or layerz_restore_version, so it lacks full when-not guidance.

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