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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds real behavioral content by disclosing the return contents (missing items, preview and checkout links), but says nothing about what happens with an invalid or non-existent draft_id or any auth requirements.

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?

A single front-loaded sentence with no filler; every clause describes an output component. It is appropriately sized for a simple read tool, though the three-item list is slightly dense.

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 does a fair job of explaining return values (contents, gaps, links), which is the main burden for a read tool. However, it leaves the lone input parameter undocumented and gives no error or edge-case behavior, so it is only adequate for the tool's complexity.

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 0% and the single parameter draft_id is never mentioned in the description, so nothing clarifies its format, where it comes from, or whether a slug or ID is accepted. The one-parameter surface makes the gap survivable but it is still uncompensated.

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?

States a specific verb ("Show") and resource ("a draft"), and enumerates what comes back: contents, what is still missing, and preview/checkout links. It does not distinguish itself from the siblings change_invitation, make_invitation, or find_designs, and the name/title uses "invitation" while the description says "draft," which takes a moment to reconcile.

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 explicit when-to-use guidance, no mention of when to prefer change_invitation or make_invitation, and no stated prerequisites such as needing an existing draft_id. The read-only nature is only implied by the word "Show."

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