abrir_login_certificado

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

With no annotations, the description carries the burden. It discloses that the SSO is visible and that certificate/PIN handling is outsourced to a local PJeOffice, which is useful behavioral context. It still omits consequences such as user interaction for PIN, side effects on session state, and failure modes.

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?

One sentence, no filler, action front-loaded; 'visível' and 'instalado localmente' add operational meaning rather than padding.

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?

The presence of an output schema and simple parameter set raises the baseline, but the definition is still thin for an interactive login tool. Missing prerequisites, user-interaction expectations, and the meaning of reiniciar mean it is only minimally viable.

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 0% and the description adds no parameter semantics. It never explains grau (1g/2g) or reiniciar, so the agent is left to infer their roles from names and enum values.

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 states a concrete action ('Abre o SSO visível') and resource ('PJeOffice instalado localmente'), making the tool's function clear. It is distinguishable from siblings like verificar_login_certificado, but it does not explicitly contrast itself with them.

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?

No conditions, prerequisites, or alternative routing are provided. The only hint is the local PJeOffice dependency; an agent cannot tell when to choose this over testar_login or verificar_login_certificado.

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