eduframe-mcp

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

No annotations are provided, leaving the description to carry the full burden of behavioral disclosure. It states 'Delete' but does not specify if the operation is permanent, if it performs cascading deletions of related records, or what authorization is required.

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 consists of a single sentence that is appropriately sized and free of redundancy, though it offers minimal information beyond what is already present in the tool name.

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 closely named siblings (`delete_affiliation`, `create_organization_affiliation`) and the destructive nature of the operation, the description lacks necessary context to distinguish this tool's specific domain and explain the consequences of deletion.

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 for its single parameter ('id'). The description text does not add parameter-specific semantics, meeting the baseline score for schemas with high description 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 states the basic operation ('Delete') and target resource ('organization affiliation record'), but fails to differentiate from the sibling tool `delete_affiliation` or clarify whether this removes the organization entity or merely the affiliation relationship.

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?

The description provides no guidance on when to use this tool versus the sibling `delete_affiliation`, nor does it mention prerequisites such as the affiliation needing to exist or the impact on associated users/organizations.

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