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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real context beyond them: newest-first ordering, the acting user's scope, this-site scope, and that both in-progress and published drafts 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?

Two sentences, zero filler, with scope and ordering front-loaded before the filter hint. Every clause carries information.

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?

Adequate for a read-only list tool whose annotations cover safety, and no output schema exists so return fields needn't be described. However, pagination semantics (limit cap of 100, offset behavior) are left unexplained for an operation that clearly paginates.

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 only 25% (only `site` is documented). The description restates the `status` filter values that the enum already supplies and never explains `limit` or `offset` pagination, leaving half the parameters undocumented in both schema and prose.

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?

Names a specific verb (List) and resource (Article Builder drafts), plus scope (acting user's, this site, in-progress and published, newest first). It is clearly distinct from get_builder_draft and save_builder_draft by implication, but never names a sibling (e.g. list_articles) to sharpen the boundary.

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?

It says the list can be narrowed with `status`, which is light operational guidance, but gives no when-to-use versus alternatives such as get_builder_draft for one draft or list_articles for published content. Usage is 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.