get_datasource

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

No annotations provided. Description only implies a read operation via 'Get' but does not disclose any behavioral traits such as authorization requirements, rate limits, or caching behavior. Carries full burden of disclosure but fails to add value.

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?

Extremely concise: three lines in docstring format. Purpose stated first, followed by parameter and return value descriptions. No unnecessary words or redundancy.

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?

Output schema exists, so return values are documented. For a simple retrieval tool with one parameter, the description is nearly complete. Missing behavioral context, but low complexity reduces the need.

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?

Only one parameter, datasource_id, described as 'The ID of the data source'. This adds minimal context beyond the schema (name and type). With 0% schema description coverage, the description does not fully compensate, but the parameter is simple enough to be self-explanatory.

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?

Description clearly states the verb 'Get' and resource 'data source', indicating retrieval of detailed information. Differentiates from siblings like get_datasource_extract_info by not specifying a narrower scope, but purpose is unambiguous.

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?

No guidance on when to use this tool versus alternatives like get_datasource_tables or get_datasource_extract_info. Agent must infer usage from tool names alone.

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