get_my_profileWhen the user asks to access or connect UniAffitti, call this tool. It starts the secure OAuth account connection when the user is not authenticated, then returns the profile without credentials or secrets.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly and non-destructive behavior. The description adds valuable context by disclosing that the tool initiates OAuth when unauthenticated and returns the profile without credentials or secrets, which goes beyond the annotation information.
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 description is a single well-structured sentence that front-loads the trigger condition and then explains the authentication behavior and return value. Every clause earns its place 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 zero-parameter tool with no output schema, the description sufficiently explains when to call it, what side effects may occur, and what is returned. It could be slightly more explicit about the shape of the returned profile, but the core information needed to invoke it correctly is present.
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, and schema description coverage is 100%, so there is no parameter documentation burden. The description appropriately avoids unnecessary parameter detail.
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 tool returns the user's profile and handles OAuth authentication, which is a specific action on a clear resource. It is distinguishable from siblings like get_account_links, though it does not explicitly contrast itself with them.
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 provides a clear trigger condition: call this tool when the user asks to access or connect UniAffitti. It gives useful context about the authentication flow but does not explicitly mention when not to use it or name alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are distinct by resource and action, but the search/catalog cluster is fuzzy: search_universities, search_cities, list_search_metadata, and list_university_campuses overlap in purpose. search_rooms and rank_room_matches also have a similar discovery role, making it easy to select the wrong tool without careful reading.
All tool names follow a consistent snake_case verb_noun pattern, with verbs like add, list, get, search, create, update, and send clearly indicating the action. This makes the tool surface highly predictable and easy to navigate.
20 tools is on the heavier side, but the count is justified by the broad scope: room search, comparison, ranking, favorites, rental requests, messaging, listing creation, and university catalog browsing. The set remains manageable because each tool maps to a distinct workflow step.
Core room-finding workflows are covered well: search, details, compare, favorites, requests, and messages. However, listing management is incomplete (create_listing has no update/delete) and messaging only supports sending a first message, with no tool for replying to an existing conversation, leaving notable dead ends.