get_article_draft

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

With no annotations, the description carries the full behavioral burden. 'Get' implies a read, but there is no statement of read-only safety, permission/auth requirements, or behavior when the draft does not exist (error vs empty). For an unannotated retrieval tool this leaves meaningful gaps.

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?

A single front-loaded sentence with no filler; the resource and scope come first. It is efficient, though extremely terse given everything left unsaid.

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?

No output schema means the description should explain what a 'draft' return contains, and no annotations means behavior must be disclosed; neither is done. With two undocumented required params and no return-value context, the definition is under-specified for a retrieval 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 description coverage is 0% and both required parameters (siteSlug, postSlug) are only self-descriptive by name. The description does not explain that these identify the target draft, what format slugs take, or whether the values are case-sensitive, so it fails to compensate for the coverage gap.

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 ('Get'), a specific resource ('NexusPress article draft'), and a qualifier ('existing'), which distinguishes it from create_article_draft and update_article_draft. It does not explicitly address the list_publications/categories siblings, so sibling differentiation is only partial.

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 phrase 'for review' hints at intent but gives no explicit when-to-use guidance. Nothing tells the agent how this differs from list_publications or when a draft should be fetched rather than listed or checked via check_draft_seo.

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