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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered and the bar is lower. The description adds real value by disclosing the payload shape (HTML article body, selected title, featured image), which substitutes for the absent output schema. It stops short of covering auth, site scoping, or not-found behavior.

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?

Two sentences, no filler, and the payload enumeration is front-loaded right after the verb. The second sentence immediately converts the payload into actionable next steps.

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 no output schema, the enumerated field list is exactly what an agent needs to know what comes back, and annotations cover the read-only profile. Minor gaps remain: no guidance on failure when draftId is invalid, and no mention of the site-scoping requirement beyond the required schema parameter.

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 50%: only 'site' is documented in the schema, and draftId has no description. The description implicitly characterizes draftId as a builder-draft identifier by saying it can be handed to publish_article_from_builder, which is modest added meaning, but it says nothing about the site parameter or ID format.

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 with scope: 'Read one Article Builder draft in full,' then enumerates exactly what 'full' contains (brief, titles, selected title, outline, written article with HTML, keywords, featured image). This clearly separates it from list_builder_drafts and delete_builder_draft in the sibling set.

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?

Gives explicit downstream routing: use the returned pieces as arguments to the step tools, or pass the draftId to publish_article_from_builder. That is clear context for why an agent would call this. It does not, however, state how to obtain a draftId (e.g., list_builder_drafts) or what to do if the draft does not exist.

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