eduframe-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether this is a read-only operation, what data the 'teacher record' contains, what happens if the ID is not found (error behavior), or whether the operation is idempotent.

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 extremely brief (four words), but this brevity constitutes under-specification rather than efficient communication. The single sentence fails to earn its place by not conveying any information beyond the tool name itself.

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 existence of 'get_teachers' (plural) and the lack of an output schema or annotations, the description should clarify that this returns a single teacher object by ID. It omits this crucial distinction and provides no hint about the return value structure or content.

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?

The input schema has 100% description coverage ('ID of the teacher to retrieve'), so the schema fully documents the parameter. The description adds no additional semantic context about the parameter, meeting the baseline expectation for high-coverage schemas.

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 'Get a teacher record' is tautological, essentially restating the tool name 'get_teacher'. While it identifies the verb (Get) and resource (teacher record), it fails to distinguish from the sibling tool 'get_teachers', leaving ambiguity about whether this retrieves a single record by ID or a collection.

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?

No guidance is provided on when to use this tool versus 'get_teachers' (for listing multiple teachers) or other teacher-related operations. There is no mention of prerequisites, such as needing to obtain the teacher ID from another call first.

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