tigergraph__fetch_vector

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

No annotations are provided, so the description carries the burden. It mentions using GSQL, which implies a query execution, and highlights a limitation of REST API, but it does not disclose potential performance impacts, read-only nature, or error behaviors.

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 followed by a brief note. It is well-structured and to the point without unnecessary detail.

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 description adequately explains the tool's purpose and the key limitation it addresses. While it doesn't elaborate on output format or edge cases, the schema provides parameter details, making it sufficient for an agent to decide when to use 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?

The schema covers all 5 parameters with clear descriptions. The tool description adds no additional parameter-specific semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 clearly states the tool fetches vertices with vector data using GSQL PRINT WITH VECTOR. It also notes that vector attributes cannot be fetched via REST API, which distinguishes it from other vertex-fetching tools like tigergraph__get_node.

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 note that vector attributes cannot be fetched via REST API implicitly guides the agent to use this tool when vector data is needed, but it does not explicitly state when to use alternatives like get_node for non-vector fetches.

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