MCP Kafka Schema Reg

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

No annotations are provided, so the description carries the full burden. It mentions 'interactive' and 'elicitation,' hinting at user prompts or step-by-step behavior, but doesn't disclose critical traits like whether it's read-only or destructive, authentication needs, rate limits, or what happens during migration. The description adds some context but is insufficient for a mutation tool with zero annotation coverage.

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 brief and front-loaded with the main purpose in the first sentence, followed by a clarifying sentence. It avoids unnecessary words, but could be more structured by explicitly listing key behaviors or parameters. Overall, it's efficient but slightly under-specified.

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 complexity (7 parameters, mutation tool), lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't explain what 'context migration' involves, the return values, error conditions, or how elicitation works. For a tool with such rich input schema and no structured support, more detail is needed to guide the agent effectively.

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 schema provides no parameter details. The description doesn't mention any parameters or their meanings, failing to compensate for the coverage gap. With 7 parameters (2 required), the agent receives no guidance on what 'context,' 'dry_run,' 'migrate_all_versions,' etc., mean or how they affect the migration.

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 tool performs 'Interactive context migration with elicitation for missing preferences,' which provides a general purpose (migrating context interactively) but lacks specificity about what 'context' means or what resources are involved. It distinguishes from sibling 'migrate_context' by mentioning interactivity and elicitation, but the distinction is somewhat vague without explaining what 'context' migration entails.

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 implies usage 'When migration preferences are not specified,' suggesting it's for cases with missing configuration, but it doesn't provide explicit guidance on when to use this versus alternatives like 'migrate_context' or other migration tools in the sibling list. No exclusions or prerequisites are mentioned, leaving the agent with minimal direction.

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