Quién soy

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

No annotations are provided, so the description carries the full burden. It clearly states that the returned user is from the MCP session token, not the browser's, which is a key behavioral distinction. It also implies no side effects. No contradictions.

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?

Single sentence, no wasted words, front-loaded with the key action. Perfectly concise for a simple tool.

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 tool has no parameters, no output schema, and a straightforward purpose. The description fully explains what it does and how the result differs from other user lookups. No further information is needed for correct invocation.

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 description does not need to explain them per se. However, it adds value by clarifying that the output is the user associated with the MCP session, which is beyond what the empty schema provides. Baseline 4 is appropriate.

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 states the verb 'Devuelve' (Returns) and the resource 'usuario' (user), and specifies the context 'asociado al token del agente (sesión MCP), no la del navegador', which distinguishes it from any browser-based user query. This is specific and differentiates from sibling tools like login or get_studio.

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?

The description implies the tool is used to get the current user identity, but it does not explicitly state when to use it versus alternatives (e.g., if another tool also returns user info). There is no guidance on exclusions or prerequisites. However, the tool has no parameters, so misuse risk is low.

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