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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that it reads the user's drafts via a PostgREST GET endpoint, but it does not cover auth requirements, pagination defaults, ordering, or rate limits, earning only partial credit beyond annotations.

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 sentences, front-loaded with purpose. The second sentence ('Estuary control-plane table drafts') slightly restates 'draft workspaces' and the endpoint line is technical but useful, so it is effective though not maximally tight.

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 list tool with full parameter schema coverage and readOnlyHint, the description covers what is listed and the scoping to user drafts. It omits pagination/ordering behavior, but no output schema exists and the operation is straightforward.

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 the single limit parameter is fully documented in the schema. The description does not mention limit or add any syntax, format, or default details, 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?

It states a specific verb ('List') and resource ('the user's draft workspaces'), and the parenthetical defines drafts as staging areas for catalog edits before publishing, which helps distinguish from list_draft_specs and list_catalog. However, it does not explicitly contrast with those siblings or clarify the exact difference from list_draft_specs.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The parenthetical 'staging areas for catalog edits before publishing' implies a review workflow, and 'user's draft workspaces' implies scoping, but alternatives are not mentioned.

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