edubase_get_user_group

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds no behavioral context beyond what annotations provide, missing an opportunity to reinforce the safe read-only nature.

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 concise sentence, but lacks any structure (e.g., sections, examples) that could aid comprehension. It is functional but not optimally helpful.

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?

Given the tool has an output schema, explicit return value details are not required. However, the description omits context like what constitutes a 'group' or potential variations (e.g., single vs. multiple groups).

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?

Schema description coverage is 100%, with 'user' described as 'user identification string'. The tool description adds no extra meaning for the parameter, meeting baseline but not surpassing it.

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 'Get user's group.' which clearly indicates the action and resource. It effectively distinguishes from siblings like 'edubase_get_user' which gets user details, but doesn't elaborate on what the group data entails.

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?

No guidance on when to use this tool versus alternatives. With many sibling 'get' tools (e.g., edubase_get_user_classes, edubase_get_user_organizations), the description should clarify when to retrieve the group specifically.

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