get_draft

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

With no annotations, the description carries the full burden. '''Get''' implies a read-only operation and '''including its body''' discloses a key response trait, but it does not explicitly mention authentication, error behavior, or other response characteristics. Still, the operation is simple and low-risk.

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?

The description is a single, front-loaded sentence with no wasted words. Every part contributes either the action, the scope, or the key return detail.

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 fetch operation with fully described required parameters, the description adequately conveys what is returned. It lacks an explicit output structure, but '''including its body''' covers the most important payload detail, and the tool has no output schema to lean on.

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 input schema already documents all three parameters (id, domain, localPart) with meaningful descriptions, so schema coverage is 100%. The description itself adds no additional parameter semantics beyond the schema.

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 states a clear verb-resource pair: '''Get a single draft'''. Adding '''including its body''' clarifies that this returns the full draft contents, distinguishing it from list_drafts and other sibling draft tools.

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?

Usage context is implied: '''single draft''' and '''including its body''' suggest this is for fetching one complete draft rather than listing drafts. However, no explicit when-to-use or when-not-to-use guidance or alternatives are mentioned.

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