Get Nacos config detail

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-obvious behavior: compatibility with Nacos 1.x/2.x/3.x and the raw-text-body return on Nacos 1.x. It does not enumerate every return field, but it goes beyond what the annotations provide.

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?

Two sentences with the core read action and identity fields front-loaded, followed by version compatibility and the return-format caveat. Every sentence earns its place and there is no redundant restatement of the schema.

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, the description usefully explains that the tool returns 'full content and metadata' and clarifies the Nacos 1.x raw-body behavior. It does not enumerate metadata fields or error cases, but for a simple config-fetch tool this is reasonably complete for an agent to call it correctly.

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 description coverage is 100%, so the input schema already documents all three parameters, including the namespace default behavior. The description adds the identity relationship ('identified by dataId + group + namespace') and single-entry scope, but it does not materially deepen the meaning of the parameters beyond the 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 opens with a specific verb 'Read' and names the exact resource: 'full content and metadata of a single configuration entry'. It also lists the identifying fields (dataId + group + namespace), which clearly distinguishes this from sibling search/list/history tools that operate over multiple entries or historical versions.

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 phrasing 'single configuration entry' and the need for exact identifiers imply this tool is for fetching one known config rather than discovering or browsing configs. However, no sibling tool is named and no explicit when-to-use/when-not-to-use guidance is provided, so the usage context is only implied.

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