MCP Kafka Schema Reg

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

No annotations are provided, so the description must fully disclose behavioral traits. 'Delete' implies a destructive mutation, but the description does not specify if this action is reversible, requires specific permissions, has side effects (e.g., on related schemas), or what happens upon success/failure. This lack of detail is a significant gap for a destructive tool with no structured safety hints.

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 a single, direct sentence with no wasted words, making it highly concise and front-loaded. It immediately states the tool's action and resource, which is efficient for quick comprehension, though this brevity contributes to gaps in other dimensions.

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 tool's destructive nature, 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It fails to address critical aspects like behavioral risks, parameter meanings, or expected outcomes, leaving the agent under-informed for safe and effective use in a complex environment with many sibling tools.

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 0%, so the description must compensate by explaining parameters. It mentions 'schema context' but does not clarify the 'context' parameter's meaning or the optional 'registry' parameter's role (e.g., whether it specifies a target registry or defaults to a global one). Without this, the agent lacks semantic understanding beyond the bare schema types.

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 schema context' clearly states the verb ('Delete') and resource ('schema context'), making the purpose understandable. However, it lacks specificity about what a 'schema context' entails or how it differs from similar resources like 'context' in sibling tools (e.g., clear_context_batch, migrate_context), which reduces clarity. It avoids tautology but remains vague in scope.

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. With sibling tools like clear_context_batch, clear_multiple_contexts_batch, and migrate_context that might handle similar resources, there is no indication of when delete_context is preferred, such as for single deletions versus batch operations or irreversible actions. This absence of context leaves the agent without usage direction.

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