MCP Kafka Schema Reg

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'application-level batching' and compliance, but fails to describe critical behaviors: whether this is a destructive operation (implied by 'clear'), what permissions are needed, rate limits, error handling, or what 'clear' actually means in practice. The warning symbol adds some caution but lacks specifics.

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 appropriately brief with two sentences. The first states the core purpose, and the second adds important compliance context. There's no unnecessary repetition or fluff, though it could be more informative given the complexity of the operation.

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 batch operation tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is severely inadequate. It doesn't explain what the tool returns, how batch operations work, error scenarios, or provide enough context for safe and effective use despite the operation's apparent complexity.

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 0% schema description coverage and 4 parameters, the description provides no information about any parameters. It doesn't explain what 'contexts' should contain, what 'registry' refers to, the meaning of 'delete_contexts_after' versus 'dry_run', or how these interact. The description fails to compensate for the complete lack of schema documentation.

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 clearly states the action ('Clear multiple contexts') and target ('in a registry'), with the verb 'clear' being specific. However, it doesn't explicitly differentiate from sibling tools like 'clear_context_batch' or 'delete_context', leaving some ambiguity about when to choose this specific batch operation.

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 like 'clear_context_batch' or 'delete_context', nor does it mention prerequisites or exclusions. The only contextual note is about 'application-level batching' for compliance, which doesn't help with tool selection.

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