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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral value by disclosing the exact payload (metadata, revision, preview link, status) and, importantly, that 'Game HTML is excluded' — a negative disclosure that prevents a wrong expectation.

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 tight sentences with no filler. The return payload is front-loaded and the exclusion clause follows immediately, so nothing is buried.

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?

With no output schema, the description correctly enumerates the returned fields, and annotations cover the safety profile. Minor gaps remain around error behavior for an invalid/unknown token and the token's expected format, but an agent has enough to invoke it correctly.

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?

There is one parameter with 0% schema description coverage, so the description must carry the burden. It identifies the input as a 'management token' and frames it as the identifier of the draft being read, but gives no format, sourcing, or validation detail beyond that.

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 gives a specific verb-plus-resource ('Returns a private draft's metadata') and enumerates the returned fields, which resolves the ambiguity between the tool name 'get_gift' and its title 'Read a draft'. It does not explicitly differentiate itself from siblings such as get_made_game or export_gift, which share the draft-reading space.

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 'for the supplied management token' hints at a prerequisite, but there is no explicit statement of when to use this tool versus alternatives like get_made_game or export_gift, and no exclusions. The agent is left to infer routing from the tool name alone.

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