list_scheduled_emails

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that only unsent queued messages are included and hints at a workflow via cancellation, but it does not state that the operation is read-only, how results are ordered, or what a response contains.

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?

Two short sentences carry useful information without filler. The core definition is front-loaded, and the pointer to cancel_scheduled_email is a relevant, non-redundant addition.

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 list tool with one optional parameter, the description is minimally adequate: an agent can infer what to call and roughly what it returns. However, the lack of parameter explanation, explicit read-only behavior, and return-shape context leaves meaningful gaps, especially because no output schema or annotations compensate.

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 schema has one optional parameter, limit, with 0% schema description coverage, and the description does not mention limit at all. The parameter name and numeric constraints suggest its meaning, but the description adds no semantic value beyond what the schema already exposes.

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 clearly identifies the resource as 'Messages queued to send later but not yet sent,' which pins down what this tool operates on. It distinguishes scheduled emails from sent or broadcast emails, though it relies on the tool name for the explicit 'list' verb.

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?

The description implies when to use the tool: to view unsent queued messages. It also points to cancel_scheduled_email as the follow-up action, which gives useful context, but it does not explicitly contrast this tool with alternatives like list_emails or list_broadcasts.

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