Identify the currently authenticated UGent Ufora user. Use it to verify which student account is active before reading courses, grades, or announcements.
Return the currently authenticated UGent Ufora user.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a read-only identity lookup, but does not disclose required authentication scope, what happens if unauthenticated, or the response shape (since no output schema exists). Moderate context is missing.
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, well-formed sentence with no waste. The purpose is front-loaded and clear.
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, no-annotation, no-output-schema tool, the description is minimal. It does not describe return values (since no output schema) or error conditions, which could be useful for an agent to know. However, the core purpose is fully stated.
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 baseline is 4. The description does not need to explain parameters, and schema coverage is 100% (though empty). No additional parameter meaning is required.
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 ('Return') and resource ('currently authenticated UGent Ufora user'). It is clearly distinguishable from siblings like doctor or list_courses, which deal with diagnostics or course data.
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?
Implied use is to check identity when authenticated, but the description offers no explicit when-to-use guidance or alternatives. A sibling like 'doctor' might serve as a diagnostic alternative, but this is not addressed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.