EduBase MCP Server

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

While annotations correctly indicate readOnlyHint=false and idempotentHint=false (meaning multiple calls create multiple resources), the description adds no behavioral context beyond the verb 'Create'. It does not mention side effects, failure modes, or that the operation is non-idempotent despite this being critical information.

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 with no redundant words. However, given the tool's complexity (5 parameters with conditional requirements), it may be overly terse rather than appropriately concise.

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?

The description identifies the resource being created and leverages the comprehensive schema (100% coverage) and existing output schema. However, it fails to mention the LMS-specific parameter requirements or distinguish from update operations, leaving gaps in contextual completeness for an integration creation 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, the baseline is 3. The description implicitly maps to the 'type' parameter by mentioning 'API or LMS', but adds no further semantics about parameter relationships (e.g., that 'lti' and 'platform' are conditional on LMS type) or data formats 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 states a clear verb ('Create') and resource ('API or LMS integration'). It implicitly distinguishes from sibling operations like delete/get/patch through the verb choice, and from other POST operations (e.g., post_integration_keys) by specifying the core resource. However, it does not clarify when to use this versus patch_integration for updates.

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 (e.g., patch_integration for modifying existing integrations), nor does it mention prerequisites like checking for existing integrations. The conditional requirement of 'lti' and 'platform' parameters for LMS types is left entirely to the schema.

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