eduframe-mcp

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

The description adds no behavioral context beyond the annotations. It fails to explain non-idempotency (annotations indicate idempotentHint: false), what validation occurs (e.g., for the nested address_attributes), or side effects of creation.

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?

While brief (3 words), it is under-specified rather than efficiently concise. Given the complexity (4 parameters including a nested address object), the description is inappropriately sized and fails to front-load critical context.

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?

Inadequate for the tool's complexity. The nested address_attributes object and required course_location_id suggest business logic relationships that are completely unexplained. No output schema means the description should clarify what gets created, but it doesn't.

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 75% schema description coverage, the parameters are reasonably documented in the schema. The description adds no parameter context, but the high schema coverage means it doesn't need to compensate significantly. Baseline score applies.

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 meeting location' is tautological, essentially restating the tool name without elaborating what distinguishes a 'meeting location' from similar resources like 'course_location' (a sibling tool) or what this entity represents.

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 provided on when to use this versus alternatives (e.g., update_meeting_location), nor prerequisites (e.g., requiring an existing course_location_id), nor relationships between meeting locations and course locations.

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