estado-de-sesion

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

With no annotations, the description must carry the behavioral load; it does disclose one meaningful trait — 'Nunca muestra cookies' — a security/privacy guarantee. However, it does not state that it is a read-only probe, nor what the session/CV states can be, leaving gaps for an unannotated tool.

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 short sentences, front-loaded with the primary purpose, and the cookie disclaimer earns its place as a privacy note. No filler.

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 zero-parameter status tool this is nearly sufficient, but with no output schema the description should say what values 'sesión válida' and 'estado de la hoja de vida' can return (e.g. logged-in/out, CV complete/missing) so an agent can interpret 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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate and it correctly implies a parameterless status check.

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?

Names a specific check: whether an elempleo session is valid plus the state of the 'hoja de vida'. This is clearly distinguishable from iniciar-sesion (which starts a session) and from perfil/CV tools, though 'estado de la hoja de vida' remains slightly ambiguous (completeness? upload status?).

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 explicit statement of when to call this versus iniciar-sesion or ver-perfil-maestro, and no prerequisites (e.g. 'call before postular-a-oferta to verify login'). Usage is only inferable from the tool name and the word 'Indica'.

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