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

readOnlyHint=true already establishes the safe-read profile, so the bar is lower. The description adds useful context (backed by the control-plane table draft_specs, PostgREST GET /draft_specs) but says nothing about pagination behavior, ordering, result shape, or auth requirements beyond what the annotation and limit param imply.

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 compact clauses, front-loaded with the core purpose and then the entity definition. The trailing PostgREST/table detail is slightly implementation-flavored but minimal and not wasteful.

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?

A simple two-parameter read tool with a fully documented schema and no output schema. The description supplies the conceptual meaning of a 'draft spec' and its scope, which is enough for an agent to call it correctly; only return-shape/ordering details are 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?

Schema coverage is 100%: both draft_id (the draft to list staged specs for) and limit (PostgREST max rows) are fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 ('List') and resource ('staged spec entries within a draft') and defines the entity concretely as an insert/replace of a catalog entity pending publication. This scope ('within a draft') distinguishes it from estuary_list_drafts (which lists the drafts themselves) and estuary_get_catalog_spec (a single published spec). An agent can tell what it returns without opening the schema.

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 implied: you call it with a draft_id to enumerate that draft's staged specs. However, there is no explicit when-to-use vs alternatives guidance, no mention of when the result is empty, and no routing against siblings like estuary_list_publications or estuary_get_catalog_spec.

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