Expands related links over HTTP for a given query, helping AI agents turn search results into follow-up sources.
Expand related links through HTTP.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| caller | No | mcp | |
| context | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.6.5Input schema / properties / callerAdded value: +{
+ "default": "mcp",
+ "title": "Caller",
+ "type": "string"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. It mentions HTTP but does not disclose whether the tool makes external requests, requires authentication, has rate limits, follows redirects, or has side effects.
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 a single front-loaded sentence with no wasted words, but it is under-specified rather than effectively concise. It lacks the detail needed for correct invocation.
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 has three parameters, no annotations, and 0% parameter description coverage. Although an output schema exists and reduces the need to explain return values, the description still omits critical invocation and behavioral context.
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% for all three parameters, and the description provides no information about `query`, `caller`, or `context`. With low coverage, the description should compensate but does not.
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 verb ('Expand') and resource ('related links') plus a transport ('through HTTP'), but 'expand' is ambiguous and the scope is not clarified. It does not distinguish this tool from the sibling `expand_links_v2` or explain what kind of expansion occurs.
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, when not to use it, or which sibling tool to prefer. The presence of `expand_links_v2` and related tools makes this omission significant.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.