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

With readOnlyHint=true already declaring the safety profile, the description adds genuinely useful context beyond annotations: the outcome semantics of job_status (queued/success/failed), the fact that these are control-plane table rows, and the underlying PostgREST endpoint. It does not cover ordering or pagination behavior, so it falls short of a 5.

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 short fragments, front-loaded with the core purpose and free of filler. The trailing 'PostgREST: GET /publications' is implementation detail that is marginally useful but not strictly necessary.

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 single-parameter, no-output-schema list tool, the description supplies the missing return-value semantics (job_status values) and the data domain, which is enough for correct invocation. It could still mention ordering or volume expectations but nothing essential is absent.

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?

There is only one optional parameter and schema description coverage is 100%, so the schema already documents 'limit' fully. The description adds no syntax, default, or ordering guidance beyond that, making the baseline 3 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 names a specific verb and resource ('List publication history/status') and clarifies the unit of a row — 'each publish attempt of a draft' — which separates it from estuary_list_drafts and estuary_publish_draft. It does not explicitly name the sibling that triggers a publish, so it stops short of full 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?

Usage is only implied by the content ('publication history/status') — an agent can infer this is for checking past publish attempts, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as estuary_publish_draft or estuary_list_drafts.

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