profiles_search

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

No annotations are provided, and the description only says 'Search profiles by key'. It does not explicitly state read-only behavior, page limits, or that it searches within a single domain. The verb 'search' implies non-mutating, but other behavioral traits are undisclosed.

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 one concise sentence, immediately communicating the core action and examples without any superfluous 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?

The output schema covers return values, but the description omits how domain_name relates to the search and where to obtain it. However, for a simple search tool, the description provides minimal but sufficient context to guess the parameters' purposes.

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?

With 0% schema coverage, the description adds meaning to key_name via examples but leaves values and domain_name unexplained. Parameter names are self-descriptive, but the description does not clarify exact-match vs partial-match or the role of domain_name.

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 clearly states the tool searches profiles by key, giving concrete examples (_email, _phone, _account). This distinguishes it from sibling tools like profiles_get_profile (which fetches a single profile) and search_contacts (which searches contacts).

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 implies usage when you have a key value to match, but does not explicitly state when to use this over alternatives or what to do when you lack a key (e.g., use profiles_get_profile with ID). No exclusions or alternative tool mentions.

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