tigergraph__discover_tools

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

No annotations are present, so the description carries the burden. It discloses the tool's non-executive nature by stating that it returns a list of recommended tools and related information, not performing graph mutations. It does not explicitly say 'read-only' or mention auth/rate limits, but the discovery behavior is reasonably transparent.

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 compact and well-structured with short bullet groups for use cases, returns, and an example. Every sentence serves a purpose and there is no redundant or verbose content.

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?

There is no output schema, but the description compensates by listing what is returned: recommended tools with descriptions, use cases, complexity ratings, prerequisites, related tools, and example parameters. The example input helps ground usage, though error behavior and exact response format are not specified.

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 already covers all three parameters with examples and descriptions, including the category filter values and the task_description examples. The tool description adds only a repeated example and no additional parameter-level meaning, so it does not exceed the baseline for full schema coverage.

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 identifies the tool as a discovery mechanism: 'Discover which TigerGraph tools are relevant for your task.' It specifies the resource (relevant TigerGraph tools) and the verb (discover), and its purpose is distinct from the many operational sibling tools by focusing on recommendation rather than execution.

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 'Use this tool when' section explicitly lists three conditions, such as being unsure which tool to use or wanting to explore capabilities. It does not explicitly name alternatives or state when not to use it, but the conditions are concrete enough for an agent to decide.

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