copy_data_source

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

No annotations; description carries full burden. States 'clone' which implies non-destructive copy, but does not disclose if data is copied, if permissions carry over, or if the cloned data source requires activation. No mention of output schema or side effects.

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 (3 words) but at the expense of completeness. Lacks any structure or additional sentences that would clarify behavior. Under-specification reduces usefulness.

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?

Despite having an output schema (not shown), the description does not explain what the clone operation returns. For a single-parameter tool with no annotations, the description leaves significant gaps in understanding the tool's effect and outcome.

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 has one required parameter (data_source_id) with 0% schema coverage from description. The description does not explain the parameter's purpose, format, or how to obtain it. Parameter semantics rely solely on its title 'Data Source Id', which is minimal.

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 says 'Clone a data source.' Verb 'clone' and resource 'data source' clearly indicate action and object. Distinguishes from sibling 'copy_job' by resource type. However, it lacks detail on what cloning entails (e.g., creates a copy with same properties, potentially without data).

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 vs. alternatives like 'copy_job' or 'validate_data_source'. No prerequisites, exclusions, or context for typical use cases provided.

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