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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds one real behavioral fact — results are scoped to 'the user's' drafts, not all drafts — but the 'Estuary control-plane table drafts' and 'PostgREST: GET /drafts' fragments are implementation trivia that tell an agent nothing actionable. No pagination or ordering behavior is disclosed.

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 with the core purpose front-loaded, so it reads quickly. The trailing PostgREST endpoint and table-name fragments are near-zero value for an agent and could be dropped without loss.

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 one-parameter read-only list tool this is largely adequate, but with no output schema the description never hints at what a draft record contains (id, name, timestamps) or how results are ordered/paginated. An agent knows what the tool lists but not what it gets back.

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% and there is only one optional integer parameter, so the schema fully carries the load. The description adds no syntax, default, or range guidance for limit, 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?

States a specific verb and resource ('List the user's draft workspaces') and even defines what a draft is ('staging areas for catalog edits before publishing'), which is genuinely clarifying vocabulary. However, it does not differentiate itself from close siblings like estuary_list_draft_specs or estuary_list_publications, so an agent still has to guess which listing matches its intent.

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 parenthetical about drafts being pre-publish staging areas implies the usage context (use this before publish_draft, and to review unpublished work). But there is no explicit when-to-use or when-not-to-use statement, and no routing to alternatives such as list_draft_specs for the contents of a draft.

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