list_search_company

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral context beyond the purpose—no mention of pagination, result format, or how the query parameter behaves. It does not disclose anything about the response or side effects (though there are none). Given the low bar set by annotations, this is still minimal.

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, with only two sentences and the endpoint. It is front-loaded with the main purpose. However, it is so sparse that it borders on under-specification rather than concise efficiency. The structure is acceptable but leaves out critical detail.

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?

For a search tool with two optional parameters, the description is incomplete. It does not explain how the query parameter is used, what a typical search entails, or how pagination works. Even though an output schema exists, the lack of parameter semantics and usage guidance makes it insufficient for an agent to call it correctly in varied contexts.

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 0%, so the description must compensate by explaining the parameters. It only says 'query: Query parameter.' and 'page: Query parameter.'—this is a tautology that repeats the parameter name without adding meaning. It does not clarify that query is the search term or that page controls pagination. No added value beyond the schema itself.

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 action and resource: 'Search for companies.' This is a specific verb+resource pair, and the tool name itself distinguishes it from siblings like list_search and list_search_keyword. It also includes the exact endpoint, reinforcing the purpose.

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?

There is no guidance on when to use this tool versus alternatives such as list_search or list_search_keyword. It does not mention that this is specifically for company search, nor does it explain any exclusions or prerequisites. The agent is left to infer from the name.

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