eduframe-mcp

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

While the description doesn't contradict the annotations (readOnlyHint=true aligns with 'Get'), it adds no behavioral context beyond what annotations already provide. It fails to disclose error handling (e.g., invalid ID), return value structure, or cache behavior, despite the absence of an output schema.

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 (three words), which could be efficient, but the grammatical error ('an meeting') and lack of specificity mean it doesn't earn its place effectively. It is front-loaded but undersized for the tool's 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?

Given the absence of an output schema and the presence of similarly-named sibling tools, the description should clarify that this retrieves a single specific record by ID. It fails to address these gaps, leaving critical contextual information missing.

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 meeting location to retrieve'), establishing a baseline score. The description itself mentions no parameters, but does not need to compensate given the complete schema documentation.

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 provides a basic verb ('Get') and resource ('meeting location'), but remains vague about scope (singular vs. plural retrieval). It fails to distinguish from sibling 'get_meeting_locations' and contains a grammatical error ('an meeting' instead of 'a meeting'), detracting from clarity.

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 regarding when to use this tool versus alternatives like 'get_meeting_locations' (which lists all locations) or 'create_meeting_location'. There are no prerequisites, exclusions, or workflow hints mentioned.

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