horizon_torn_getCompaniesSearch

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 does not state that this is a read-only operation, mention pagination behavior (despite limit/offset parameters), or indicate rate limits or response caching, leaving important gaps.

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 concise at one line, but it is too minimal to be helpful. It prioritizes brevity over clarity, omitting important context and thus not earning its place efficiently.

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 7 parameters, no output schema, and many sibling tools, the description is insufficient. It does not explain return format, pagination, or how filters work, leaving the agent underinformed.

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 description loosely covers the name parameter but adds no new meaning beyond the schema for limit, offset, filters, timestamp, comment, or key. Since schema coverage is 71% and the filters parameter is already well-documented in the schema, the description adds minimal value.

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 'Search companies by name or other criteria', which indicates the verb and resource but is vague about scope. It does not distinguish this tool from siblings like horizon_torn_getCompaniesList or horizon_torn_getCompanyProfile, which also involve company data retrieval.

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 versus alternatives. The description does not mention prerequisites, typical use cases, or exclusions, leaving an agent unsure about selection criteria.

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