ofw_list_drafts

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

Annotations already declare readOnlyHint=true, and the description adds value by explaining the cache dependency. It discloses that the tool reads from a local cache and requires a sync if empty, which goes beyond the annotation. No contradictions.

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 extremely concise: two short sentences. The first sentence front-loads the core purpose, and the second provides essential usage guidance. No extraneous information.

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 list tool with no output schema, the description adequately covers the main functionality and a critical precondition. It lacks details on return format or attributes, but given the simplicity, it is nearly complete.

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 input schema covers both parameters with descriptions (100% coverage). The tool description does not add any additional meaning to 'page' or 'size' beyond what is in the schema, so it does not exceed the baseline.

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 states 'List draft messages from the local OurFamilyWizard cache,' specifying the verb 'list' and the resource 'draft messages.' It distinguishes from siblings like ofw_save_draft (write) and ofw_list_messages (non-drafts) by focusing on drafts and the local cache.

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 provides a precondition: 'Call ofw_sync_messages first if the cache is empty.' This guides when to use the tool and suggests an alternative action. However, it does not explicitly exclude scenarios where ofw_list_messages might be more appropriate, though the context is clear.

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