Listing data sources

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

The description adds behavioral context beyond annotations by specifying required permissions and the ability to filter built-in data sources. Annotations already indicate read-only, idempotent, non-destructive behavior, which the description aligns with. No contradictions.

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 concise with three sentences. It front-loads the purpose, then provides a filter hint and permission requirement. Every sentence adds value, though the first sentence is somewhat redundant with the title.

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 covers the main use case, a key filter, and required permissions. It lacks details on pagination, error handling, or output format, but an output schema exists. Given the tool's simplicity and annotations, it is reasonably complete.

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 coverage is 100%, so baseline is 3. The description adds a hint about the 'builtin' parameter's purpose (filter built-in data sources) but does not explain 'verbose' or 'response_format' further. The schema already provides descriptions for all parameters, so the description adds marginal value.

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 tool 'Gets a list of existing data sources.' It uses specific verb+resource ('Gets a list of data sources') and distinguishes from sibling tools like create or delete data sources.

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 provides explicit guidance on filtering built-in data sources via the 'builtin' parameter and specifies required permissions ('Perm: manage_data_sources, manage_reports'). It does not explicitly state when not to use, but the permission requirement implies conditions for use.

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