edubase_get_user_group

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

Annotations already declare the tool as read-only and non-destructive. The description 'Get user's group' adds no behavioral details beyond that, such as what constitutes a group or the format of the response. While the output schema exists, the description itself offers no transparency.

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 extremely concise, but it under-specifies. It is efficient but lacks important context that would make it more helpful. A score of 3 reflects the trade-off between brevity and completeness.

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?

Despite having an output schema, the description fails to provide contextual completeness. It does not explain what 'group' refers to (e.g., primary group, all groups) or how this tool differs from multiple sibling user getters. The agent may not know when to select this tool over others.

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 schema has 100% coverage with a clear parameter description ('user identification string'). The tool description does not add any further meaning to the parameter, so a baseline of 3 is appropriate.

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 'Get user's group' clearly states the action (get) and resource (user group). However, it does not differentiate from sibling tools like 'edubase_get_user' or 'edubase_get_user_classes', which also retrieve user-related data. A 5 would require explicit distinction.

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 is provided on when to use this tool versus alternatives such as 'edubase_get_user' or 'edubase_get_user_organizations'. The description lacks context for appropriate deployment.

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