aya_agentes_obter_atual

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

The description adds the useful fact that data comes from persistent memory and that the tool returns the current agent/task, which goes slightly beyond the tool name. However, with no annotations present, the description carries the full burden and does not mention read-only behavior, missing-data behavior, or possible side effects.

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 entire description is a single, front-loaded, information-dense sentence. Every word contributes to explaining what the tool does and where it reads from, with no redundancy.

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 parameterless getter, the description is mostly sufficient: it names the source and the object returned. It does not describe the output shape or what happens when no current agent/task exists, but this is a minor gap given the tool's simplicity.

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 already complete and there is nothing for the description to clarify. This matches the baseline of 4 for parameterless tools.

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 clearly identifies the tool as retrieving ('Retorna') the current agent/task from persistent memory. It names a specific resource and gives a concrete action, though it does not explicitly distinguish itself from related siblings such as aya_memoria_obter_contexto_retomada or aya_agentes_adquirir_lock.

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?

There is no guidance about when to use this tool instead of the many related memory, agent, or checkpoint tools. No conditions, exclusions, or alternative recommendations are provided.

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