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

With no annotations, the description carries the full burden for behavioral disclosure. It communicates the search mechanism ('semantic search') and scope ('all refined knowledge databases'), which implies a read-only operation, but it does not explicitly confirm non-mutation, return characteristics, or limitations like rate limits or filtering behavior.

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 concise sentence that front-loads the action and scope. It loses a point because 'edge vector' is unexplained jargon that may reduce clarity for an agent.

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 three parameters, no annotations, and no output schema, the description is too sparse to be complete. It does not explain the result format, the meaning and behavior of topK and domain, or how this general semantic search relates to the twelve sibling tools, so an agent has to make several assumptions before calling it.

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 only 33%, and the description adds no parameter-level meaning beyond what the schema already exposes. topK and domain, including the domain enum values, are left for the agent to infer from names and defaults; the description does not explain how 'all refined knowledge databases' maps to the domain parameter.

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 and resource ('Perform edge vector semantic search') and defines the scope ('across all refined knowledge databases'), so an agent can tell it is a general retrieval tool rather than a domain-specific sibling. It is distinguishable from the sibling tools by the word 'all', but the jargon term 'edge vector' is unexplained and slightly obscures the meaning.

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 phrase 'across all refined knowledge databases' implies this is the broad search tool, and the sibling names suggest narrower domain-specific alternatives. However, the description never explicitly states when to choose this tool over a specific refinery_* tool or when not to use it.

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