List scheduled Notes

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable behavior beyond annotations: the response is sorted soonest-first and includes publication status plus failure reasons. This gives the agent useful expectations about output content.

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 sentences with zero filler. The core action and ordering are front-loaded, and the additional output detail is compact and informative.

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 read-only list tool with one optional filter parameter and no output schema, the description provides sufficient context: what is listed, ordering, and the status/error information returned. Annotations cover safety and idempotence, so no critical gap remains.

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 only parameter, status, is fully documented in the schema with its enum and 'Omit to see all of them.' The description adds no extra parameter semantics, but schema coverage is 100%, so the agent gets what it needs.

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 a specific verb ('List') and resource ('Notes queued by schedule_note'), distinguishing it from sibling tools like list_scheduled_posts and list_notes. It also clarifies the ordering ('soonest first') and what is shown, making the tool 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?

The description clearly implies when to use this tool: to view notes created via schedule_note, with a filter for status. It does not explicitly mention alternatives such as list_scheduled_posts, but the resource definition provides enough context to avoid confusion.

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