ofw_list_messages

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

Annotations already declare readOnlyHint=true; description adds that it reads from a local cache (not real-time), pagination is offset-based, and cache may have 1000+ messages. 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?

Three concise sentences: main purpose, filtering support, pagination advice, and prerequisite. No wasteful words, information is front-loaded.

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?

No output schema, but description covers input semantics and cache behavior. Missing what the return format looks like, but given it's a list tool and 6 params are well-described, it's 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?

Schema coverage is 100% so baseline is 3. Description adds case-insensitive substring behavior for 'q', sent_at semantics for since/until, and folder name options for folderId. Also recommends using filters over pagination.

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 it lists messages from a local cache, supports filtering by folder, date range, and substring search. It distinguishes from sibling tools like ofw_get_message (single message) and ofw_list_drafts (different resource).

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?

Provides explicit advice to prefer filters over pagination for large caches and to call ofw_sync_messages first if cache is empty or stale. Lacks explicit comparison to other list tools for different resources, but context signals and sibling list suffice.

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