contacts_other_search

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Search other contacts', with no information about side effects, mutability, or response behavior. The description does not add value beyond the name.

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 a single short sentence but it is essentially a tautology of the tool name. It is concise but lacks substance; ideally, it should be slightly more informative while remaining brief.

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 search tool with no output schema and minimal context, the description should clarify what 'other contacts' refers to and typical use cases. It fails to do so, leaving the agent with insufficient information to understand the tool's proper context.

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% (both 'query' and 'readMask' are described). The description does not add additional meaning beyond the schema; it repeats the function name. Baseline of 3 is appropriate.

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 states it searches 'other contacts', which is a specific category distinguished from siblings like 'contacts_list' and 'contacts_search_directory'. However, 'other contacts' is not clearly defined, leaving ambiguity about what exactly this searches.

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 is provided on when to use this tool versus alternatives such as 'contacts_search_directory' or 'contacts_list'. There is no mention of when not to use it or any conditions.

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