List CNBS Data Sources

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. The description adds value by specifying the return content (name, description, status) beyond what annotations provide, but it does not cover any potential limitations like pagination or performance.

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 extremely concise: three sentences covering purpose, return value, and an example. Every sentence is necessary and front-loaded with the key action.

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 the absence of parameters and output schema, the description is adequately complete. It explains what the tool does and what it returns. A minor gap is that it does not mention typical use cases or that this tool is for discovery before using other data-fetching tools.

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?

With zero parameters, the baseline is 4. The description correctly adds no parameter details since none exist, and the schema already covers 100% of parameters.

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 verb '列出' (list) clearly specifies the action on the resource '数据源' (data sources). It distinguishes itself from sibling tools like cnbs_fetch_data_from_source or cnbs_search, which operate on specific sources or search within them, by indicating it lists all available 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 implies usage as a starting point to discover available data sources, but it does not explicitly state when or when not to use this tool or mention alternatives. For example, it could clarify that this is for browsing all sources before narrowing down with other tools.

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