get_user_info

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing about side effects, permissions, or whether it operates on the authenticated user versus a specified one. For a zero-parameter tool the risk is low, but the lack of any behavioral statement leaves real ambiguity about whose data is returned.

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 short sentence that front-loads the resource and then lists the fields; there is no filler or redundancy. It is efficient, though the brevity borders on under-specification rather than crisp conciseness.

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?

An output schema exists, so explaining return values is unnecessary, and the description's field list is a reasonable summary. However, with no parameters and no annotations, the description should clarify that it returns the current student's profile, which it never states.

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 takes no parameters, so the schema has nothing to document and the baseline is 4. The description's field enumeration relates to the returned payload rather than to inputs, which is harmless but contributes nothing to parameter understanding.

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 states a specific resource (student information) and enumerates the fields it conveys (name, group, course, faculty, specialty), so the agent knows what data it retrieves. The verb 'get' is only implied, and there is no explicit differentiation from siblings, though the resource differs from get_attendance and get_schedule.

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 on when to use this tool versus get_attendance or get_schedule, nor any indication of prerequisites. The agent must infer usage entirely from the tool name and field list.

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