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

readOnlyHint=true already tells the agent this is a safe read. The description usefully adds that entries are staged and pending publication, plus the backing table and PostgREST endpoint, but says nothing about ordering, pagination defaults, or what an empty draft returns.

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, front-loaded fragments with no wasted prose. The trailing implementation details (table name, PostgREST route) are developer-oriented trivia that add little for an agent, keeping it just short of a 5.

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 two-parameter, read-only list tool with no output schema, the description covers what is listed and its meaning, and annotations cover the safety profile. Only the return shape and pagination/ordering behavior go unmentioned.

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 parameters (draft_id, limit) are already documented in the schema. The description adds domain framing about what draft_id scopes but no syntax or format detail beyond the schema, 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+resource ("list the staged spec entries within a draft") and clarifies what a spec entry is ("an insert/replace of a catalog entity pending publication"), which separates it from estuary_list_drafts and estuary_get_catalog_spec. It does not name the sibling tools explicitly, so differentiation requires a little inference.

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 by the scoping phrase "within a draft" and the required draft_id, but there is no explicit when-to-use/when-not-to-use or naming of alternatives such as estuary_list_drafts. An agent can infer the context but is given no routing guidance.

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