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. It only indicates a write operation via 'Adds' but fails to specify side effects (e.g., whether existing elements are replaced or appended), return values, permission requirements, or rate limits.

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. It is appropriately front-loaded with the action verb and conveys the core purpose without waste.

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 complex polymorphic input schema with nested object structures and two distinct element types, the description is inadequate. It lacks explanation of the element types, nesting behavior, and output expectations (no output schema provided), leaving significant gaps for an agent attempting to construct valid inputs.

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 50% schema coverage, the description partially compensates by referencing 'set of elements', which maps to the elements array parameter. However, it does not explain the polymorphic nature of elements (CourseElement vs BlockElement), the nested structure of BlockElement, or the relationship between course_id and planned_course_id.

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 clearly states the action (Adds) and target (set of elements to a program edition). It implies batch operations via 'set of elements', distinguishing it from singular 'get' or 'create' siblings. However, it does not explicitly clarify the distinction between adding elements to an edition versus creating program element definitions (create_program_element).

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 like create_program_element or get_elements_of_program_edition. It omits prerequisites (e.g., requiring an existing program edition) and does not indicate idempotency or error conditions.

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