evolution_chat_find_contacts

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

With no annotations provided, the description carries full burden of behavioral disclosure. It fails to mention whether the tool requires authentication, whether it returns all contacts by default, if there are rate limits, or what side effects (none expected) exist. Minimal description leaves agent guessing.

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?

Description is a single short sentence, achieving maximum conciseness. The key action 'Find contacts' is front-loaded. However, it may be too terse, sacrificing informativeness for brevity.

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?

Given the nested 'where' parameter with no explicit structure in the description, no output schema, and no annotations, the description is insufficient for an agent to understand the full input and output behavior. Missing details on filter logic, instance requirement, and result format.

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 both parameters having descriptions. The 'where' parameter includes an example in the schema. The tool description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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 'Find contacts, optionally filtered.' The verb 'find' and resource 'contacts' distinguishes it from sibling tools like evolution_chat_find_chats or evolution_chat_find_messages. However, it lacks explicit differentiation such as 'Use for contacts, not chats.'

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 to use this tool vs alternatives. Does not mention when to filter or not, nor provides context about results or pagination. The description merely states an optional filter without explaining its purpose or typical use.

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