eduframe-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description mentions 'Delete' but does not clarify whether this is a permanent hard delete, what happens to pending webhook deliveries, or whether the operation is idempotent. For a destructive operation, this lack of safety context is a significant gap.

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 concise at three words, avoiding verbosity. However, the single sentence fails to earn its place by merely restating the tool name rather than adding value. While appropriately sized for a simple single-parameter tool, it represents under-specification rather than efficient information density.

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 annotations, output schema, and the presence of numerous sibling webhook tools, the description is incomplete. It fails to explain the implications of deletion (e.g., immediate cessation of calls), error scenarios, or how this operation fits into the webhook lifecycle management alongside create_webhook and update_webhook.

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 with the 'id' parameter clearly documented as 'ID of the webhook to delete'. Since the schema fully describes the parameter semantics, the baseline score of 3 applies. The description adds no additional parameter context (e.g., format constraints, where to obtain the ID), but is not penalized given the complete schema 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 'Delete a webhook' is essentially a tautology that restates the tool name 'delete_webhook' with slight grammatical variation. While it identifies the verb (delete) and resource (webhook), it fails to distinguish this tool from sibling operations like update_webhook or create_webhook, and provides no scope clarification (e.g., permanent vs. soft delete).

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 alternatives such as update_webhook or deactivate_teacher. It lacks prerequisites (e.g., checking webhook status before deletion), warnings about irreversibility, or conditions where deletion might fail.

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