UAAR University MCP Server

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

Annotations provide key hints: readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds minimal behavioral context beyond this, only specifying the input method ('using CNIC'). It doesn't contradict annotations, but offers little extra insight into rate limits, error handling, or response format.

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, efficient sentence that directly states the tool's function and input method. It is front-loaded with the core purpose and avoids any unnecessary words, making it highly concise and well-structured.

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 annotations covering safety and idempotency, an output schema exists (so return values are documented elsewhere), and only one parameter is clarified in the description, the description is reasonably complete. However, it lacks usage guidelines and differentiation from siblings, which slightly reduces completeness for an agent's decision-making.

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%, but the description mentions 'using CNIC', which clarifies the meaning of the single parameter 'cnic' beyond the schema's basic type. Since there's only one parameter and the description adds this semantic detail, it meets the baseline for adequate coverage without fully compensating for the schema gap.

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 ('check admission status') and the required input ('using CNIC'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_admission_form_status' or 'preview_admission_form', which could involve similar admission-related queries, leaving some ambiguity about its specific scope.

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 'get_admission_form_status' or 'get_admission_requirements'. It lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage based on the name alone.

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