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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful context about what the call returns (connector catalog entries with titles, descriptions, logos) and the backing endpoint (PostgREST GET /connectors), but says nothing about pagination or result size relative to the 'limit' parameter.

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 compact and front-loads the core purpose, with the endpoint reference trailing at the end. The final two fragments ('Estuary control-plane table connectors. PostgREST: GET /connectors.') are slightly telegraphic but cost little.

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?

For a simple read-only catalog listing with no output schema, the description covers the essential return shape but omits pagination behavior despite exposing a 'limit' parameter. It is adequate but leaves the agent to infer paging semantics.

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 both 'limit' and 'recommended' are already documented in the schema. The description adds no syntax or format detail beyond mentioning the recommended filter, so the baseline 3 is appropriate.

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 the connector catalog — available capture/materialization Docker connectors') and even enumerates returned fields (titles, descriptions, logos). It is clear what the tool does, though it never explicitly distinguishes itself from the sibling 'estuary_list_connector_versions', which an agent could easily confuse it with.

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 only usage hint is 'Optionally filter to recommended connectors,' which restates a parameter rather than telling the agent when to reach for this tool. There is no guidance on when to prefer it over siblings like estuary_list_connector_versions or estuary_get_catalog_stats, and no stated prerequisites.

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