whoami

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by naming the exact fields returned, but says nothing about authentication/session requirements, failure modes when no user is logged in, or timezone format — context that matters for a session-scoped lookup.

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?

A single front-loaded sentence with no filler, and the enumerated field list earns its place because there is no output schema. Slightly long as one sentence but nothing is wasted.

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?

With no parameters and no output schema, the description carries the burden of describing the return payload and does so by listing all four fields, which is sufficient for an agent to decide to call it. Missing only session/auth caveats and error behavior.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly conveys that no arguments are needed by framing the result as the implicitly-logged-in student.

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?

States a specific verb ('Obtiene') and resource (the logged-in student's profile on Campus Virtual UTN Mendoza) and enumerates the returned fields (name, email, enrolled courses, timezone). No sibling tool overlaps with this 'current user' capability, so differentiation is implicitly clear, though it is never stated explicitly.

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?

Usage is only implied: an agent can infer this is the tool to call when it needs identity/context about the current session, and that other tools (list_courses, get_grades) are the resource-specific alternatives. There is no explicit 'use this when…' guidance or statement about prerequisites such as an active session.

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