eduframe-mcp

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

Description adds no behavioral context beyond what annotations provide. Does not explain implications of idempotentHint:false (risk of duplicates), error conditions when user/account doesn't exist, or what the tool returns.

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?

Extremely brief (three words), but contains wasteful redundancy/error. Front-loaded structure is appropriate, but severe under-specification makes it ineffective.

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?

Incomplete for a creation tool with 3 parameters and no output schema. Lacks explanation of affiliation semantics, business rules (can a user have multiple affiliations?), and differentiation from organization-level affiliations.

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?

Schema description coverage is 100%, clearly documenting the user-account relationship and key_contact flag. Description adds no parameter details, but baseline adequacy is met by the schema itself.

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 states the action ('Create') but contains redundancy/typographical error ('affiliation affiliations'). It fails to define what an affiliation represents (a user-account relationship evident from schema) or distinguish from sibling tool `create_organization_affiliation`.

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?

Provides no guidance on when to use this tool versus alternatives like `create_organization_affiliation`, `update_affiliation`, or prerequisites for creating affiliations.

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