superchat_search_contacts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral limitations beyond annotations: it is a read-only POST, exact-match only, and cannot combine conditions or do fuzzy matching.

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?

Two sentences, both dense with useful information. The core purpose is front-loaded, and the limitations/alternative are packed into the second sentence with no wasted words.

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 input schema fully documents all six parameters and the annotations cover read-only behavior, the description is mostly complete. The main gap is that there is no output schema and the description does not explicitly describe the result shape or pagination return fields, but the schema context and tool name make these reasonably inferable.

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 description coverage is 100%, so the input schema already documents field enums, value types, pagination cursors, limit, and identifier. The description adds the 'exact equality match' semantics and friendly field names, but it does not add significant parameter-level detail beyond the schema.

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 a specific verb and resource: 'Find contacts with one exact equality match on email, phone, Instagram ID or a custom attribute.' It clearly defines the matching mode and scope, and the final sentence distinguishes it from list_contacts, so an agent can tell it apart from siblings.

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?

The description explicitly says this tool does not support fuzzy name search or combining conditions, and it names list_contacts as the alternative for browsing. This is direct when-to-use and when-not-to-use guidance with a concrete alternative.

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