list_drafts

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

The readOnlyHint annotation is consistent with the 'List' action, but the description adds no behavioral context beyond that annotation. It does not mention ordering, pagination, empty results, or any side effects, so the agent gets no extra transparency from the text.

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 brief and front-loaded with the core action, so it is technically concise. However, the '(unconfigured)' prefix adds noise, and the terseness reflects under-specification rather than economical completeness.

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-only list tool, the description still leaves key gaps: what 'account' refers to, what a draft is in this context, and what the response contains. With no output schema and no parameter coverage, the agent cannot reliably invoke this tool without guessing.

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 description entirely omits what 'account' means, what format it should take (ID, email, name), or how it filters the returned drafts. The agent is left without any semantic guidance for the only required parameter.

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 action ('List') and resource ('drafts') are clear, and the sibling tools make it apparent this is the draft-listing tool. However, the description does not define what counts as a draft or what scope the list covers, and the '(unconfigured)' prefix adds ambiguity.

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?

No guidance is given on when to use list_drafts versus siblings like list_labels, list_accounts, search, or create_draft/update_draft. There is no mention of prerequisites, expected account state, or scenarios where another tool would be preferable.

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