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

Beyond the readOnlyHint annotation, the description discloses that results are scoped to entities 'the user can read' (a permission filter), that metadata includes connector and last-publication info, and names the backing source (live_specs_ext / GET /live_specs_ext). It does not describe pagination behavior despite limit/offset params, but it adds meaningful read-scope context.

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?

Three sentences, front-loaded with the core purpose and entity list before the filter and implementation notes. The PostgREST endpoint and view-name references are marginal utility for an agent but do not bloat the description significantly.

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 carries the return-shape burden and does so reasonably by naming the entity types and the connector/last-publication metadata. It falls slightly short on paging/return-volume expectations, but is complete enough to call correctly.

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, offset, spec_type, and name_prefix. The description restates the name-prefix and spec_type filters but adds no syntax detail (e.g., wildcard behavior is left to the schema) and omits limit/offset, so it does not meaningfully exceed the schema baseline.

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 gives a specific verb and resource ('List live catalog entities') and enumerates the entity types (captures, collections, materializations, tests), plus the payload shape (connector + last-publication metadata). It implicitly separates 'live' entities from draft-oriented siblings but never names an alternative explicitly, so it stops just short of full sibling differentiation.

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?

It notes the filters are optional and scoped to a catalog-name prefix and spec_type, which hints at when filtering matters. However, it offers no guidance on when to use this versus estuary_list_drafts, estuary_get_catalog_spec, or estuary_list_publications, leaving the routing decision to inference.

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