EduBase MCP Server

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

Annotations indicate readOnlyHint=false (write operation) and destructiveHint=false. Description adds valuable behavioral context not in annotations: the link reuse/caching policy ('returned instead'). Does not mention link expiration or auth requirements, but covers the critical idempotency-like behavior.

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?

Two sentences total. First establishes purpose; second provides behavioral nuance. Zero redundancy or filler. Information density is optimal.

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 presence of output schema and annotations covering safety hints, description adequately covers the operation's purpose and caching behavior. Minor gap: does not define what constitutes 'valid' (TTL/expiry) for existing links.

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% description coverage ('external unique question identifier'), so the structured data fully documents the parameter. Description does not add parameter-specific semantics, which is acceptable given the high schema coverage baseline.

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?

Description uses specific verb 'Generate' with clear resource 'download link for exporting the question' and specifies format 'JSON'. Distinct from sibling 'edubase_get_question' which retrieves data directly, while this creates an export artifact.

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 behavioral guidance via 'If a previous valid link exists, it will be returned instead,' implying caching behavior. However, lacks explicit guidance on when to choose this over 'edubase_get_question' or other question retrieval methods.

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