test_query_data_source

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

No annotations provided; description only states 'query' with no behavioral info (e.g., read-only, side effects, pagination behavior). Schema shows pagination params but description does not elaborate.

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 short but under-specified. Conciseness sacrifices essential details; the description is merely a label.

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?

With 5 parameters and an output schema (not described), the description is woefully incomplete. No info on output format, data source context, or how to craft filter/sort JSON.

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%, meaning no descriptions in schema properties. The description does not explain any parameters (data_source_id, filter, sorts, cursors, page_size), failing to add value beyond the schema.

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 '[test] Query a data source' provides a vague verb+resource but lacks specificity to distinguish from sibling tools like default_query_data_source or test_query_database. The '[test]' prefix hints at testing but no further context.

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 test variant vs default query or other query tools. No context for appropriate use cases or alternatives.

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