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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value by decoding draft lifecycle states and field meanings (kind, show_at, error), but it omits the implicit filtering behavior, ordering, and pagination that a listing tool needs.

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?

It is a single dense paragraph with the resource front-loaded, and no sentence is pure filler. However, it spends its length field-by-field while omitting the operational details an agent most needs, so the allocation of space is misjudged.

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 filtered list tool with a non-obvious default status and a limit cap, the description should explain filtering and result size. With no output schema and no parameter documentation anywhere, the agent has to open the schema to learn the tool only returns ready drafts by default.

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 there are two parameters, yet the description never names 'status' or 'limit'. The status enum values appear only as prose describing draft outcomes, not as a filter argument, and 'all' and the 100-item maximum go unmentioned.

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 the resource precisely ('drafts proposed by assistants') and enumerates the outcome states, so an agent knows what is being listed. It never uses the verb 'list' nor distinguishes itself from siblings like draft_reply or withdraw_draft, but the scope is unmistakable.

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 statement of when to call this versus draft_reply, withdraw_draft, or list_follow_ups. Critically, the description never mentions the status filter or its default of 'ready', so an agent cannot tell that the default call only returns ready drafts rather than all of them.

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