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. While 'Get' implies a read-only operation, the description lacks explicit safety guarantees, error handling details (e.g., behavior when ID doesn't exist), or return value structure.

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?

At 4 words, it is brief, but this is under-specification rather than efficient conciseness. The phrase 'an user' contains a grammatical error, and the sentence adds no value 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 presence of siblings like 'get_users', 'create_user', and 'update_user', the description should clarify this is a singular retrieval operation. Without an output schema, some mention of return behavior would improve completeness.

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 schema has 100% description coverage ('ID of the user to retrieve'), so the baseline is 3. The description adds no additional parameter context, but the schema adequately documents the single required parameter.

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 an user record' is a tautology that restates the tool name with minimal variation. It fails to distinguish this tool from sibling 'get_users' (which likely returns a list) or specify that this retrieves a single user by ID.

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 single-record lookup versus 'get_users' (list operation), or versus 'get_current_educator'. No mention of prerequisites (e.g., knowing the user ID) or error conditions.

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