search_messages

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

Discloses that search uses SQLite FTS, results are relevance-ranked, only locally stored messages are searched, and pagination is available. No annotations provided, but description covers behavioral traits thoroughly.

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?

Six sentences, front-loaded with core purpose, then technical details, then usage guidance. No redundant or unclear statements.

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?

Covers purpose, constraints, parameters, and usage thoroughly. Lacks output format details but is essentially complete for a standard search tool.

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% with good descriptions; description adds context like E.164 format for sender and pagination usage, exceeding minimal 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 the tool performs full-text search across locally stored messages by keyword or phrase, and distinguishes itself from chronological browsing via get_conversation.

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?

Explicitly states when to use (searching for specific messages/topics across conversations) and when not to (use get_conversation for chronological browsing), with parameters like sender, limit, offset explained.

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