eduframe-mcp

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

While annotations indicate this is a non-idempotent write operation (readOnlyHint: false, idempotentHint: false), the description adds no behavioral context about side effects, duplicate creation risks, or what constitutes a successful 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?

The single sentence is not verbose, but it severely under-specifies the tool. It fails to earn its place by providing any actionable information 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?

For a complex mutation tool with 7 parameters including nested objects (address, signup answers) and relationships (labels), the description is severely incomplete. It lacks output expectations, error conditions, or domain context needed to invoke this tool correctly.

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 71% schema description coverage, the schema carries most of the documentation burden for parameters like `address_attributes` and `signup_answers_attributes`. The description adds no parameter semantics, but the baseline is adequate given the schema's decent coverage.

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 an account' is a tautology that merely restates the tool name. It fails to distinguish this tool from sibling `create_user` or clarify what type of account is being created (billing, customer, organizational, etc.) in this complex system.

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 on when to use this tool versus alternatives like `create_user` or `create_lead`, nor are prerequisites mentioned. The agent cannot determine if this is for initial registration, administrative account creation, or bulk imports.

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