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.

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

With no annotations, the description must carry the behavioral load. It usefully discloses that this is a write requiring user authorization and that it verifies afterward, but it omits what happens on failure, whether a mismatched expected_finish aborts the write, or whether the operation is idempotent.

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, front-loaded with the operation and its scope; nothing is padded. The telegraphic style costs a little clarity but wastes no space.

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, and the description covers goal, precondition, and auth. However, for a four-parameter mutation with 0% schema coverage and no annotations, leaving the parameter set and failure behavior unexplained is a meaningful gap.

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% across four required parameters, so the description is the only source of meaning. It hints that 'finish' takes MATTE or GLOSSY, but page_id, draft_id, and especially expected_finish are left completely undefined.

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 (Save) and resource (MATTE/GLOSSY cover finish) scoped to an existing draft, and adds a verify step. It is clearly distinct from kdp_tabs and kdp_draft_status, though it never explicitly names them.

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 gives a precondition ('on an uncertified existing draft') and an authorization rule ('User-authorized writes only'), which is real usage guidance. It stops short of saying when to prefer this over alternatives or what to do when the precondition fails.

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

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 disclose one real trait — that Chrome may prompt the owner to allow the connection — which is genuinely useful operational context. It says nothing about read-only status, what happens if the connection is denied, or how to retry.

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, purpose front-loaded, caveat second. Every clause carries information and there is no filler.

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 explained, and there are no parameters to document. Still, for a tool whose name is opaque ('KDP tabs'), the description leaves the domain and the consequence of the Chrome permission prompt unexplained, which an agent may need to call it confidently.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. No misleading parameter guidance is present.

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 (List) and resource (KDP tabs) with a scope qualifier ('only KDP tabs'), which distinguishes it from a generic tab-listing tool. However, 'KDP tabs' is never defined (browser tabs vs. KDP project views), so the agent must infer the domain from the sibling names.

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?

There is no statement of when to use this versus kdp_draft_status or kdp_set_cover_finish, nor any prerequisite or exclusion. The only usage signal is the implicit fact that it is a listing operation.

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