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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile well. The description adds value beyond annotations by enumerating what data the draft details include and by disclosing the prerequisite relationship to mutation tools. No contradiction with annotations; the description adds meaningful context on top of a strong annotation baseline.

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 sentences with zero filler. The purpose and content scope are front-loaded in the first sentence, and the sequencing instruction follows in the second. It's appropriately sized for the tool's simplicity, though the enumeration is slightly long-winded.

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 simple read tool with one parameter, strong annotations covering safety, and no output schema, the description is nearly complete. It discloses the returned content and the usage prerequisite. The only minor gap is no explicit statement about what a not-found draftId returns, but this is acceptable given the tool's simplicity.

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% with a single parameter (draftId) fully documented in the schema, so the baseline is 3. The description doesn't add parameter-specific detail beyond the schema, but none is needed for a single well-documented ID parameter. The description's content enumeration indirectly explains what the ID resolves to, which is adequate.

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 uses a specific verb ('Get') with a clear resource ('draft details') and enumerates the exact content returned: saved signee details, signature placements, form field values, invitation settings, and AI assistant configuration. This specific enumeration clearly distinguishes it from sibling tools like get_draft_file, get_draft_file_url, and list_drafts.

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 second sentence gives explicit when-to-use guidance: 'Always call this before update_draft, send_draft, or delete_draft.' This is strong sequencing instruction. It doesn't state explicit exclusions (e.g., 'for a list of drafts use list_drafts'), but the enumeration of content plus the mutation-prerequisite guidance provides clear context for selecting this tool.

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