tigergraph__get_data_source

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

The description 'Get information' clearly implies a read-only operation with no side effects. However, no explicit statement about safety or lack of mutation is included, and there are no annotations to reinforce this.

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 clear sentence with no filler or redundant information. It is appropriately concise and well-structured.

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 is adequate for a simple retrieval tool but does not specify what information is returned, how errors are handled, or whether the data source must already exist. The lack of an output schema increases the need for more detail, which is not provided.

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?

Both parameters are described in the schema, achieving 100% coverage, but the descriptions are minimal and add no extra context beyond the parameter names. The 'profile' description is slightly more helpful, but overall semantics are basic.

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 action ('Get') and the target ('a specific data source'), making the tool's purpose unambiguous. It does not enumerate what information is returned, but the intent is clear.

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 does not explicitly contrast this tool with the sibling 'get_all_data_sources' or explain when to prefer one over the other. The name and description imply the distinction, but no direct guidance is provided.

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