EduBase MCP Server

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds the membership scope ('member of') which clarifies the query behavior, but doesn't address pagination, caching, or authorization requirements beyond the structured hints.

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 single sentence is efficient with no redundant words, front-loading the action. However, given the extensive sibling list with similar names, it is arguably too minimal—one additional sentence distinguishing from edubase_get_classes would improve utility without significant bloat.

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?

For a single-parameter read operation with existing output schema and comprehensive annotations, the description meets minimum viability. However, it lacks guidance on the user identifier format and doesn't clarify the relationship to edubase_post_user_classes (add membership) versus this retrieval tool.

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?

With 100% schema description coverage ('user identification string'), the baseline is 3. The description implies the user parameter by referencing 'a user' but adds no format specifications, examples, or validation rules beyond what the schema provides.

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 uses a specific verb 'List' with clear resource 'classes' and distinguishes from siblings via the membership constraint 'a user is member of'. This clearly differentiates it from edubase_get_classes (general listing) and edubase_get_class_members (reverse relationship of class-to-users).

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 like edubase_get_classes (all classes) or edubase_delete_user_classes. It omits prerequisites or context about requiring a valid user identifier.

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