get_certificate_info

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

Since no annotations are present, the description carries the burden of behavior. It discloses that the tool returns only metadata and explicitly warns that it does not return the certificate itself for security reasons. This is informative, though it could also mention authentication requirements or the read-only nature of the operation.

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 concise sentences with no redundancy. The key scope ('información del certificado') is front-loaded, and the security caveat is placed at the end without wasting words.

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 no-parameter, read-only info tool, this is complete: it states what data is returned, when to use it, and the critical limitation. No output schema exists, but the listed fields provide enough expectation of the result.

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?

There are zero parameters, so the schema is fully covered (100%) and the baseline is 4. The description adds no parameter-level detail because none is needed.

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 a specific verb ('Obtiene información') and identifies the resource ('certificado digital de la empresa'), enumerating the returned fields: titular, RUT, fecha de vencimiento y estado. This clearly distinguishes it from sibling tools like get_document or get_user_info by the subject matter.

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?

It explicitly states when to use the tool: 'Usar cuando el cliente pregunta por su certificado o si está por vencer.' It does not name an alternative tool or an explicit when-not condition, but the use context is clear enough for an agent to route correctly.

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