catalog_history

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful context about what is inspected (immutable history, lineage, run records) and that the catalog is schema-v2, but it does not explain pagination, limit behavior, or how much history is returned.

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 front-loaded sentence that states the main action and scope without filler. It could be structured slightly better to separate purpose from parameter behavior, but it is appropriately sized.

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?

The tool has three parameters, low schema description coverage, and no output schema. The description covers the high-level result categories and one parameter, but omits the required `db` argument and the meaning/default of `limit`, which are necessary for correct invocation.

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 only 33%, and the description only clarifies the optional dataset path filter. The required `db` parameter and the `limit` parameter are undocumented in both the schema and the description, leaving essential invocation details unaddressed.

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 uses a specific verb ("Inspect") and names the resources (immutable version history, parent/child lineage, recent run records) in a schema-v2 catalog. It is clearly distinguishable from generic catalog operations, though it never explicitly contrasts itself with siblings like catalog_index or catalog_search.

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 phrase "optionally filtered to one dataset path" implies when the path parameter is useful, but there is no explicit guidance on when to choose this tool over catalog_index, catalog_search, or catalog_stats. Usage is implied rather than directed.

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