get_all_drafts

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the listing is restricted to the caller's own drafts and requires authentication. It stops short of covering read-only safety, pagination/result limits, or ordering, all of which matter for a list endpoint.

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 purpose is front-loaded in the first sentence with scope qualifiers following immediately. The trailing "GET /api/v1/drafts" and "Tags: Conversations" lines are metadata padding that adds little for an agent, but they are short.

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 zero-parameter read tool this covers the essentials of what is fetched and by whom. Because there is no output schema, the description should say something about the shape or volume of returned drafts (fields, pagination), and it does not.

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 tool takes no parameters, so there is nothing for the description to disambiguate; the baseline applies. The stated scope (all drafts, not per-conversation) is the only semantic needed, and it is present.

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 and resource plus real scoping detail: unsent reply and private-note drafts, saved by the caller, across conversations. That is enough for an agent to know exactly what comes back. It doesn't name a sibling it might be confused with, but no draft-specific alternative exists in the sibling list.

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?

"Across conversations" implies the global/my-drafts scope and "Any authenticated agent" gives an auth precondition, so usage is implied rather than stated. There is no explicit when-to-use versus when-not guidance, and no mention of when to prefer a conversation-scoped retrieval instead.

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