kdp_draft_status

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

With no annotations, the description carries the full behavioral burden; it does usefully disclose the absence of side effects (no certify/save/upload/publish). It says nothing about permissions, scoping of the draft to a page, or read-only guarantees beyond that single negative clause.

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 short sentences, zero padding, with the positive purpose front-loaded and the negative boundary second. Every clause earns its place.

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?

An output schema exists, so return values need not be described. But for a two-parameter tool with 0% schema coverage and no annotations, the description omits parameter meaning entirely, leaving a notable gap even for a simple read operation.

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 the description adds no meaning for either required parameter. An agent gets no indication of what page_id vs draft_id represent, how they relate, or what format draft_id takes.

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 (read) and resource (existing paperback draft), which is clear enough to distinguish it from the sibling mutators kdp_set_cover_finish and kdp_tabs. However, the name says 'status' while the description says 'Read an existing paperback draft', leaving slight ambiguity about whether it returns draft state or draft content.

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?

'Does not certify, save, upload or publish' establishes that this is the non-mutating option, implying it is the read path among siblings. But it never states when to call it, what it presupposes (an existing draft_id), or names an alternative to prefer in other cases.

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