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

Annotations already declare readOnlyHint true, idempotentHint true, and destructiveHint false, so the description does not need to repeat safety behavior. The description adds meaningful context: the results are 'curated editorial connections' rather than raw search output, and there is a strict dependency on prior search_graph results. This goes beyond the structured annotations without contradicting them.

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 front-loaded with the core purpose and only four sentences. However, it contains mild redundancy: 'that search alone wouldn't carefully surface' and 'that web search cannot provide' say essentially the same thing. Overall the structure is good and each sentence contributes, but trimming the duplicate claim would be more 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?

For a tool with 7 parameters and no output schema, the description gives the essential workflow context: call it after search_graph, uses valid node_ids, and explains why it is useful. The schema richly documents parameters and enums. The main gap is that the description does not specify the output shape or format of the 'connections' returned, which would be helpful especially since no output schema exists. Otherwise the context is adequate for selection and invocation.

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 every parameter is already thoroughly explained in the schema. The description reinforces that seed_node_ids must come from a prior search_graph result, but this is already explicitly documented in the input schema. The description does not add new parameter-level meaning beyond what the schema provides, justifying the baseline score.

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?

States a specific verb and resource ('discover what's connected to a trend') and explicitly enumerates what the tool surfaces: brands, technologies, locations, and cross-domain links. The phrase 'curated editorial connections that web search cannot provide' clearly distinguishes it from search_graph and other sibling tools. This is not a tautology or vague restatement of the name.

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?

The description gives clear, actionable guidance: 'Use after search_graph' and lists specific use cases such as mapping territory, finding connected brands, or understanding cross-domain relationships. It also states the hard prerequisite of requiring a node_id from a prior search_graph result. It does not explicitly name exclusion scenarios or alternatives like get_node or get_evidence, so it falls just short of the highest bar.

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