list_sources

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

With no annotations, the description fully discloses paging behavior (has_more/total, page increments), page_size cap (500), and return fields (source_id, name, engine type, account/database/schema). It also notes the default for source_type and the meaning of empty string.

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?

Three concise paragraphs each serve a distinct purpose: overview, source_type parameter, and paging mechanics. No filler, clear organization, and front-loaded purpose.

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?

Given an output schema exists, the description does not need to detail return values. It covers paging, parameter semantics, and the key decision of which sources can share a knowledge cluster. The page_size cap warning is valuable contextual completeness.

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 no parameter descriptions (0% coverage). The description compensates by explaining source_type values and default, page usage for continuation, and page_size cap. This adds essential meaning beyond the raw 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 states a specific action with a resource: 'List configured data sources (source connections)'. It clearly distinguishes from siblings like get_source (single source) and create_* tools, and clarifies one-page-at-a-time semantics.

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?

Provides clear context for use: helps identify which sources can share a knowledge cluster, and warns not to assume one page is all. However, it does not explicitly name alternative tools or when-not-to-use scenarios.

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