intelx_search_results

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

With no annotations, the description carries the full burden. It usefully discloses the authentication requirement ('Requires INTELX_API_KEY') and implies data retrieval, but it does not describe pagination behavior, possible empty results, error conditions, or response structure. More context could be added, so this is adequate but not rich.

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 with the primary action and key constraint front-loaded. Every word earns its place; no redundant or vague filler. This is appropriately concise.

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 tool is simple with three well-described parameters and no output schema. The description covers purpose, sequencing, and authentication. While it does not detail the return format, the phrase 'get actual data' plus the schema's limit/offset parameters provide enough context for an agent to select and invoke the tool correctly.

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 baseline is 3. The description adds no parameter-specific meaning beyond the schema; 'id' is already described as 'Search ID from intelx_search' in the schema. The tool description does not need to compensate for missing schema info.

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 uses a specific verb ('Retrieve results') and identifies the precise resource ('IntelligenceX search by ID'). It clearly distinguishes from siblings by stating 'Use after intelx_search', which sets it apart from intelx_search (initiation) and phonebook result 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?

Provides clear usage context: 'Use after intelx_search to get actual data.' This tells the agent when to invoke it and the dependency on a prior search. It does not explicitly list when not to use or mention alternatives like intelx_phonebook_results, but the guidance is sufficient for typical use.

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