EduBase MCP Server

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

Annotations cover read-only, non-destructive, and idempotent properties. Description adds no context about the sensitive nature of returned secrets, security handling requirements, or whether this returns active vs. historical keys. No contradiction with annotations.

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?

Extremely brief at four words with no wasted language. While concise, the single sentence is arguably too terse to provide meaningful operational guidance beyond restating the tool name.

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?

Despite having an output schema and only one parameter, the description is inadequate for a credential-retrieval tool. Significant gaps remain regarding security implications of handling secrets and lifecycle context (retrieval vs. rotation).

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 has 100% coverage with the `integration` parameter documented as 'integration identification string'. Description adds no semantic details about parameter format or examples, meeting baseline for high 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?

States the basic action (Get) and resource (integration keys/secrets) but lacks specificity about scope (requires specific integration ID) and does not differentiate from sibling `edubase_post_integration_keys` which likely handles key generation/rotation rather than retrieval.

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?

Provides no guidance on when to use this retrieval endpoint versus the creation endpoint (`edubase_post_integration_keys`), nor any prerequisites for accessing sensitive credential data.

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