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

Annotations only declare readOnlyHint=true, so the description usefully adds the data source (Estuary control-plane view catalog_stats) and the underlying PostgREST call, which helps an agent understand the aggregation model and time-grain semantics. It does not mention auth needs, pagination defaults, or what happens with a nonexistent catalog_name, so it stops short of full disclosure.

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?

Front-loaded with the core purpose, followed by scope and data-source notes across three tight sentences. The internal view/PostgREST references are arguably dispensable but are compact and aid debugging.

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?

With no output schema, the description compensates by enumerating the returned metric fields and the per-row grain, so an agent knows what a call yields. It lacks guidance on defaults for date range and result limits, which is a minor gap for a read-only stats 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?

Schema description coverage is 100%, so all five parameters (grain enum, limit, ts_start/ts_end, catalog_name) are already documented in the schema. The description restates grain and the optional timestamp bound but adds no format or interaction detail beyond that, matching the baseline for high-coverage schemas.

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?

States a specific verb (Get) and resource (catalog stats) and enumerates the exact metrics returned — bytes/docs read+written, usage_seconds, warnings/errors/failures, txn_count — plus the grain dimension. This clearly distinguishes it from sibling read tools like estuary_get_catalog_spec or estuary_list_catalog.

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 context ('Optionally bound by a timestamp range') but never states when to choose this over the catalogue-listing or spec-reading siblings, nor any exclusion or prerequisite. Usage is inferable from the metric list rather than stated.

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