get_data_source

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

No annotations provided; description carries full burden. Clearly indicates it is a read operation (retrieval). Explains concepts like data source vs. data asset vs. connection, aiding understanding. Does not explicitly mention rate limits or idempotency, but appropriate for a GET tool.

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?

Well-structured with sections and bullet points. Provides needed details without excessive verbosity. Minor redundancy in explaining data source vs. asset, but overall efficient.

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?

Comprehensive for a retrieval tool with no output schema. Covers purpose, usage guidelines, parameter semantics, and related tools. No gaps identified.

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 0%, so description must compensate. It lists both parameters in Args section with brief descriptions (domain ID, data source ID), but adds little beyond the schema field names and required status. Some context added but not rich.

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?

Clear verb ('Retrieves detailed information'), specific resource ('specific, known data source'), and explicit context. Distinguishes from sibling tools list_data_sources and get_asset.

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?

Explicitly states when to use ('when user mentions a specific data source by name, type, or context') and lists detailed information it provides. Also mentions related tools and their purposes.

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