intelx_search_results

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful non-annotation detail (requires INTELX_API_KEY), but says nothing about pagination behavior or the shape/nature of returned results.

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 tight sentences with zero waste. The core action and its dependency are front-loaded, and the auth requirement is a concise trailing note.

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 read-only tool whose annotations carry the safety profile and whose schema fully documents pagination, the description supplies the essential workflow context and auth requirement. Return-format detail is largely unnecessary given the nature of the operation, though a note on result volume/paging would round it out.

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 id, limit, and offset are already fully documented in the schema. The description only echoes that the ID comes from intelx_search, adding no syntax or format detail beyond the structured fields, so the baseline of 3 applies.

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 a specific verb (Retrieve) and resource (results for an IntelligenceX search by ID), and implicitly distinguishes itself from the sibling intelx_search which initiates the search. An agent can tell this is the retrieval half of a two-step flow without opening the schema.

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?

'Use after intelx_search to get actual data' gives explicit sequencing context that selects this tool over its sibling. It stops short of naming when-not conditions or alternative result paths, but the triggering context is clear.

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