local_draft_status

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful constraint that no delivery is attempted, but says nothing about what 'state' means, whether a stale or nonexistent draft errors out, or whether the draft could change concurrently.

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?

One sentence, front-loaded with the verb and resource, with the key qualifier ('without attempting delivery') placed at the end where it does the most work. Nothing is wasted.

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 is the only place that can explain what the returned 'state' looks like (e.g., prepared/queued/sent/failed) or whether it includes recipients and timestamps. That is exactly the information an agent needs to interpret the result, and it is absent.

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 a single required parameter, draft_id, with 0% schema description coverage, so the description must carry the load. 'One local prepared email' implicitly ties draft_id to a locally prepared draft, but gives no format, source of the ID, or behavior when the ID is unknown.

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 (return the state) and a specific resource (one local prepared email), and the phrase 'without attempting delivery' implicitly separates it from send_prepared_email. It stops short of naming that sibling, but an agent can still distinguish the read-only status check from the send action.

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?

Usage is only implied: the description suggests this is how you inspect a prepared draft before delivery, and the contrast with delivery hints at when to prefer it. No explicit when-to-use/when-not, no prerequisites, and no named alternative such as send_prepared_email or prepare_email.

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