search_messages

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

No annotations provided; description is bare: 'Search iMessages by keyword'. Does not disclose read-only nature, return format, or any behavioral traits beyond the implied action.

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?

One short sentence, but it lacks structured information. Could be more informative without being verbose; currently too sparse.

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, no parameters, yet description fails to explain how the keyword is provided, what results look like, or any limitations. Incomplete for an effective tool understanding.

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?

Input schema has zero properties, yet description implies a 'keyword' parameter. This contradiction misleads the agent. Schema coverage is trivial (100% for zero params), but description adds no value and is misleading.

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?

Description clearly states 'Search iMessages by keyword', specifying the source (iMessages) and action. Differentiates from sibling search tools for other platforms, though lacks detail on scope.

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?

No guidance on when or when not to use this tool. Sibling tools include searches for other platforms, but no alternatives or exclusions are mentioned.

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