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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's sole addition, "Returns: The draft," is a vague restatement of the title and says nothing about what a draft contains, whether it includes in-progress sheet data, or what happens if the id is unknown.

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?

It is short and front-loaded with no filler sentences, but the brevity comes from under-specification rather than economy, and the phrase "the question it is on" is opaque and adds no usable 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?

Although the tool is simple (two required parameters, no output schema), the description omits the concept of a draft entirely, gives no sense of the return payload beyond a noun, and leaves no guidance for a mutation-heavy sibling set. It is not enough for an agent to call this confidently versus its neighbors.

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 100%, documenting both the draft id and the campaign slug-or-id, so the schema carries the semantics. The description adds nothing about either parameter, which is tolerable only because the schema already covers them.

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?

The description never states a verb or that this retrieves a single character draft by id; "One draft and the question it is on" only gestures at the resource. Against siblings like list_character_drafts, update_character_draft, start_character_draft and finish_character_draft, it draws no distinction, so an agent must infer the operation from the name alone.

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 when-to-use guidance, no mention of prerequisites, and no routing to list_character_drafts for enumeration or update_character_draft for writes. The only hint is the implicit singular-vs-plural contrast in the name.

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