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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description is not obliged to restate it. The description adds downstream workflow context (drafts are reused for geometry, feature tree and parameter updates, then submitted for review) but says nothing about result size, pagination, or whether drafts from other users are included.

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?

The lead sentence is front-loaded and clear, but the two trailing clauses drift into lifecycle narrative (live geometry updates, engineer review submission) that does not help an agent decide how to list drafts. Roughly half the text is tangential to the tool's actual operation.

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?

With read-only annotations and an output schema present, return values need no explanation, so the definition only had to establish scope and prerequisites, and it does both. Remaining gaps, pagination and filtering behavior, are minor for a one-parameter list tool.

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 0% for the single project_id parameter, so the description must carry some of the burden; "in an engineering project" does loosely tie the parameter to project scoping, but it adds no format, lookup, or permission detail beyond the uuid format already in the schema.

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?

"List shared Studio authoring drafts in an engineering project" gives a specific verb (list) and resource (design drafts) scoped to a project, which is enough to separate it from write-side siblings like create_design_preview or finish_design_draft. It stops short of distinguishing itself from get_design_draft, which the plural/singular pair leaves to 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?

The description supplies a precondition ("Start an External agent draft in Studio first"), which is useful orientation before calling. It gives no when-not guidance and never points to get_design_draft for fetching a single draft, so the choice among the draft-related siblings remains implied rather than stated.

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