config_get

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

No annotations are provided, so the description carries the burden of conveying safety. 'Muestra' implies a read-only operation, but it does not explicitly state that no modifications are made or whether sensitive configuration is exposed. It adds useful context about the content (rollback and history limits) but lacks deeper behavioral disclosure.

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, front-loaded sentence with no redundant words. It efficiently communicates the tool's purpose and scope with minimal verbosity.

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?

For a simple getter with no parameters and no output schema, the description adequately explains what the tool returns (server configuration with emphasis on rollback and history limits). It does not mention the response format, but given the tool's simplicity, this is a minor omission.

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?

The tool has zero parameters, so the schema is empty. The description does not need to explain parameter meaning. Baseline 4 is appropriate since there are no parameters and the description's mention of config scope adds minor value.

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 uses the specific verb 'Muestra' (shows) and identifies the resource as 'configuracion actual del servidor' (current server configuration), explicitly naming rollback and history limits. This clearly distinguishes it from related tools like config_set (which changes config) and rollback_list/history_list (which list events rather than configuration).

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 this tool is for reading current configuration, but it does not explicitly state when to use it over alternatives or mention exclusions. There is no 'when to use' guidance, but the verb 'Muestra' and the resource scope make the usage context reasonably clear.

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