intelx_search_results

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

No annotations are provided, so the description carries full burden. It only mentions the API key requirement and basic operation, omitting details about pagination, rate limits, error handling, or data freshness. Minimal behavioral disclosure.

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, zero waste. Every word is informative and necessary. The description is front-loaded with the core action and provides usage context succinctly.

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?

No output schema and no annotations, so description must be more complete. It covers the basic workflow and prerequisites but lacks details on result format, pagination behavior, and error states. Adequate for a simple retrieval tool but not fully comprehensive.

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 coverage is 100% and already documents each parameter's meaning. The description adds slight value by clarifying that 'id' is from intelx_search, but offset and limit are standard. Baseline score achieved without significant added semantics.

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 resource ('IntelligenceX search by ID'), clearly distinguishing it from sibling tools like intelx_search (which initiates the search) and intelx_phonebook_results.

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?

Explicitly states 'Use after intelx_search to get actual data' and mentions the API key requirement, providing clear sequencing context. No explicit alternatives or exclusions, but sufficient for the intended workflow.

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