Revisar la configuración

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

The readOnlyHint=true annotation already declares the safety profile, and the description's 'Muestra' verb is fully consistent with it. The description adds value beyond the annotation by specifying exactly what configuration data is exposed (including certificate expiry), which is useful context for an agent deciding whether to call this before a risky emission action. No contradictions with annotations.

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 tight sentences with zero waste. The first sentence front-loads the informational content, and the second delivers the usage rule. Every word earns its place; no fluff or repetition of the title.

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?

Complete for a zero-parameter, read-only diagnostic tool whose safety profile is already carried by annotations. The description covers what it shows and when to call it; the absence of an output schema is acceptable for a status/display tool, so nothing an agent needs to invoke it correctly is missing.

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 takes zero parameters and the schema is empty, so the baseline of 4 applies. There is nothing to document, and the description correctly avoids inventing parameter details that don't exist.

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?

States a specific verb and resource ('Muestra la configuración') and enumerates the concrete contents it reveals: data folder, CUIT, certificates with expiration dates, profile, and issuance-confirmation method. This clearly distinguishes it from siblings like ver_perfil (profile only), ver_csr (certificate only), and probar_conexion (connectivity test), so an agent can disambiguate at a glance.

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 explicit when-to-use guidance: 'Usala primero si algo falla o si el usuario está configurando' — positioning it as the first diagnostic step on failure or during setup. It does not name specific alternatives or state when not to use it, but the use conditions are concrete and actionable.

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