nacos_list_configs

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

With no annotations, the description carries full burden. It mentions 'no content by default' and optional fuzzy filtering, but does not disclose pagination behavior, response format (e.g., list of dataId strings or full objects), or whether ordering applies.

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 a single, well-structured sentence with a parenthetical clarification. It is front-loaded with the primary action and contains no fluff.

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 6 parameters, no output schema, and no annotations, the description covers the main purpose but lacks details on parameters like group, pagination behavior, and the structure of the response (what fields each config datum includes).

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 low (33%). The description adds meaning for data_id (fuzzy keyword) and hints at include_content ('no content by default'), but fails to explain group, page_no, page_size, and include_content semantics beyond defaults.

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's function: listing config dataIds in a namespace, with optional fuzzy filtering by dataId. It distinguishes itself from siblings like nacos_get_config (which retrieves a specific config) and nacos_search_config (more advanced search).

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 for listing configs but does not explicitly guide when to use this tool versus alternatives like nacos_search_config or nacos_get_config. No when-not-to-use or alternative references are provided.

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