eduframe-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a mutation, the description lacks critical details: whether the operation is idempotent, what happens if a role with the same name exists, what fields/ID are returned, or any side effects (e.g., webhook triggers).

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 concise with no filler words or redundant sentences. However, it is under-specified rather than efficiently informative. The structure is a simple sentence fragment, which is acceptable but not exemplary.

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 dense sibling tool list containing multiple teacher-related concepts (create_teacher, create_teacher_enrollment, create_teacher_role), the description fails to clarify the conceptual model. For a mutation tool with no output schema and no annotations, the description should explain the entity's purpose and relationship to other teacher entities.

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 for its single 'name' parameter. The description adds no semantic information about the parameter (e.g., naming conventions, uniqueness constraints), but baseline 3 is appropriate when the schema is fully self-documenting.

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 'Create a teacher role' is a tautology that merely restates the tool name (create_teacher_role). It fails to define what a 'teacher role' represents (e.g., a permission template, job title, or classification) or distinguish it from siblings like create_teacher or create_teacher_enrollment.

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 such as create_teacher (which creates the educator entity) or create_teacher_enrollment (which assigns teachers to courses). There are no prerequisites, exclusions, or workflow context provided.

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