UAAR University MCP Server

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

Annotations cover read-only, non-destructive, and idempotent behavior, so the description doesn't need to repeat these. It adds value by specifying the optional semester filter, which provides context on how results are scoped. No contradiction with annotations, and it complements them with practical usage detail.

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 front-loaded with the core purpose in the first clause and adds optional filtering in the second. It's appropriately sized with zero wasted words, making it easy to parse quickly.

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 low complexity (read-only query), rich annotations (covering safety and idempotency), and the presence of an output schema (which handles return values), the description is sufficiently complete. It covers the essential what and how, though it could benefit from more usage context relative to siblings.

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 adds meaning by explaining that 'student_id' is for identifying the student and 'semester' is an optional filter. However, it doesn't detail parameter formats or constraints beyond what's implied. With two parameters and no schema descriptions, this provides basic compensation but remains minimal.

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 tool's purpose: 'Get academic results for a student' specifies the verb (get) and resource (academic results), and 'Optionally filter by semester' adds scope. It distinguishes from siblings like 'get_cgpa' or 'get_transcript_request_info' by focusing on semester-specific results, though it doesn't explicitly contrast them.

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 implies usage when needing student results with optional semester filtering, but provides no explicit guidance on when to use this versus alternatives like 'get_cgpa' for GPA or 'get_transcript_request_info' for transcripts. It mentions the optional filter but doesn't clarify prerequisites or exclusions.

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