UAAR University MCP Server

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

Annotations indicate this is a non-readOnly, non-destructive, openWorld operation. The description adds minimal behavioral context by implying an 'Admin' role requirement, but doesn't elaborate on permissions, side effects, or response behavior. With annotations covering key traits, the description adds some value but lacks depth, such as error handling or creation constraints.

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 with a single sentence, front-loaded with the key action and resource. There's no wasted wording, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions.

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's complexity (6 required parameters, mutation operation) and the presence of an output schema, the description is incomplete. It lacks details on parameter meanings, usage context, and behavioral nuances, relying too heavily on structured fields without adding sufficient explanatory value.

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 0%, and the description provides no information about parameters beyond the tool name implying 'faculty member' data. It doesn't explain what 'id', 'designation', 'research_interests', etc., mean or their expected formats, failing to compensate for the low schema coverage.

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 action ('Add') and resource ('a new faculty member'), and the '[Admin]' prefix suggests administrative privileges. However, it doesn't explicitly differentiate from sibling tools like 'admin_add_department' or 'admin_add_course' beyond the resource type, missing specific scope details that would warrant a 5.

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 no guidance on when to use this tool versus alternatives, such as 'search_faculty' for lookup or other admin_add_* tools for different resources. There's no mention of prerequisites, context, or exclusions, leaving usage unclear beyond the basic action.

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