Search Companies

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

No annotations are present, so the description must carry the full burden. It states the action (search) but fails to disclose key behaviors such as what happens if both or neither parameter is provided, pagination details, or whether the search is fuzzy or exact. The description is insufficiently transparent.

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 extremely concise, consisting of two short sentences that communicate purpose and a key constraint. It is front-loaded with the verb and resource, achieving maximum clarity with minimal verbosity.

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?

With 5 parameters, no output schema, and no annotations, the description fails to provide essential context such as return format, pagination behavior, or error handling. It does not explain the Zoho criteria expression syntax, leaving the agent underinformed for effective tool use.

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?

The input schema has 100% description coverage, but the description adds critical value by stating the mutual exclusivity of 'word' and 'criteria', which is not captured in the schema. This enhances parameter semantics beyond the schema alone.

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 for companies and specifies two distinct search modes: free-text word and Zoho criteria expression. It is specific about the resource (Companies) and the verb (Search), distinguishing it from sibling search tools.

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 instructs to provide one of 'word' or 'criteria', which is a clear usage guideline. However, it does not provide context on when to choose one mode over the other or mention alternatives for searching other entities, though the sibling tools imply the entity-specific nature.

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