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 of behavioral disclosure but fails to clarify that results are paginated (despite cursor/per_page parameters), what webhook data is returned, or any rate limiting. The claim 'Get all' is ambiguous regarding pagination behavior.

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 four-word description is appropriately front-loaded with no redundant phrases. However, given the complete absence of annotations and output schema, extreme brevity becomes a liability rather than a virtue.

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 paginated listing tool with no output schema and no annotations, the description is insufficient. It fails to mention pagination behavior, default page sizes, or the structure of returned webhook objects, leaving critical operational context undocumented.

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?

Input schema has 100% description coverage for both parameters (cursor and per_page), so the baseline score applies. The description adds no parameter-specific context, but the schema adequately documents the pagination controls.

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 uses the specific resource 'webhooks' and scope modifier 'all' to distinguish from the singular sibling 'get_webhook'. While 'Get' is slightly generic, the phrase clearly identifies this as a list operation for the webhook resource.

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 plural/list endpoint versus the singular 'get_webhook', nor when to use pagination parameters versus fetching all results. The description offers no contextual cues for tool selection.

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