search_phone_calls

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

No annotations provided, so description carries full burden. Mentions it's free and undocumented, hinting at potential instability. However, fails to disclose read/write nature, rate limits, authentication needs, or pagination behavior. Significant gaps for a search tool.

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 sentences, front-loaded purpose. No wasted words. The warning about undocumented endpoint is relevant but could be integrated. Overall efficient for a simple search tool.

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, return types, and a caution. Lacks detail on pagination, result structure, error handling, and how it fits among siblings. With no output schema, more context would be beneficial. Adequate but incomplete.

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 50% (user_id and contact_id described in schema; page and per_page only have constraints). Description adds no additional meaning for parameters, doesn't explain page/per_page functionality or expected values. Does not compensate for schema gaps.

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 phone call logs' with specific verb and resource. It distinguishes from siblings like search_contacts and search_activities by focusing on phone calls. Mentions return types (records, durations, outcomes) adding specificity.

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?

Indicates it's free and an undocumented endpoint, but lacks explicit when-to-use vs alternatives or prerequisites. Does not guide on when to use this over other search tools, though the name implies phone call-specific scope.

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