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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's added value is the ownership constraint tied to the authenticated API-key profile, which signals authorization scoping. It does not say what happens on a missing or non-owned id (error vs. empty), leaving the main behavioral edge case undisclosed.

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 scope constraint is stated up front rather than buried. Nothing could be removed without losing meaning.

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 no explanation, and annotations cover the safety profile; the remaining need is the id's origin and failure behavior. The ownership scoping covers the authorization dimension well. Only the parameter semantics are missing, which is a modest gap for a one-parameter read 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% for the single required parameter 'id', so the description must carry the burden and it does not — no indication of the id format, or that it comes from list_drafts or create_draft. A bare string id with no semantics is a real gap for an otherwise simple tool.

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 ('Returns one draft') and adds a meaningful ownership scope ('owned by the authenticated API-key profile'), which implicitly separates it from list_drafts and get_post. It stops short of naming the sibling alternatives explicitly, so it lands just under a 5.

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 'one draft' hints at single-item retrieval versus the listing sibling, but there is no explicit statement of when to use this tool instead of list_drafts, get_post, or update_draft. An agent must infer the use case entirely from the singular noun.

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