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

Annotations only declare readOnlyHint and idempotentHint; the description adds the key behavioral fact that drafts can be mutated out-of-band in the browser, which is why the call must precede updates. It also signals that the result includes a version, supporting optimistic-concurrency use, consistent with idempotentHint=false. It does not describe pagination or what happens when the token is stale, which would have pushed this higher.

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 purpose and immediately followed by the operative rule. Nothing is redundant with the title or the schema, and every clause carries decision-relevant information.

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?

For a low-complexity two-parameter read with full schema coverage, an output schema, and annotations, the description supplies the one non-obvious thing: the concurrency rationale for calling it before updates. Only minor gaps remain, such as error behavior on an invalid or expired token.

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 coverage is 100% and both parameters are described there as values returned by create_poll_draft, so the description adds no parameter meaning beyond the schema. With an output schema present, the baseline 3 is appropriate.

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?

"Read the latest content and version of a draft" states a specific verb (read) and resource (draft) plus the exact scope (latest content and version), which cleanly separates it from create_poll_draft and update_poll_draft. Sibling tools are not named explicitly, so the differentiation rests on inference rather than a direct pointer.

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?

"Call this before every update" gives a concrete, prescriptive when-to-use rule tied to a real workflow (read-before-write), and the following clause explains why. There is no explicit when-not guidance, but for a two-sibling toolset the usage condition is unambiguous.

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