list_data_sources

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

No annotations provided and description only says 'list,' which implies a read operation. No disclosure of pagination, filtering, or potential limitations. For a simple list tool, more transparency on scope or ordering would help.

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?

Single sentence, extremely concise. All information is front-loaded, no filler.

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 no output schema, no annotations, and a minimal description, the tool is contextually incomplete. It doesn't explain what properties of data sources are returned or how to interpret the list.

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?

No parameters exist, so schema coverage is 100% but trivial. Description adds no meaning beyond the name; baseline is 4 but since no value is added, 3 is appropriate.

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 'Data source list.' clearly indicates the tool lists data sources. It distinguishes from siblings like get_data_source_schema which operates on a single source. However, it essentially restates the name without adding nuance.

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 list_dashboards or get_data_source_schema. The description provides no context for selection.

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