Miyabi MCP Bundle

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. It mentions the dry-run option, which adds some context, but fails to disclose critical traits like whether this is a destructive operation (implied by 'Delete' but not explicitly stated), permission requirements, error handling, or what happens on success. For a deletion tool with zero annotation coverage, this leaves significant gaps.

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 with two short sentences that are front-loaded and waste no words. Every part earns its place by stating the core action and a key usage tip.

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 of a Kubernetes deletion operation, no annotations, and no output schema, the description is incomplete. It lacks information on behavioral outcomes, error conditions, and what the tool returns, which is crucial for an agent to use it correctly in a production environment.

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 schema description coverage is 100%, so the schema already documents all parameters (resource, name, namespace, dryRun). The description adds minimal value by mentioning 'dryRun=true' as a usage tip, but doesn't provide additional semantics beyond what the schema offers, such as examples for resource types or namespace defaults.

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 verb ('Delete') and resource ('Kubernetes resource'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'k8s_apply' or 'process_kill' which might also perform deletion operations in different contexts, so it doesn't reach the highest score.

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 explicit guidance on using 'dryRun=true to preview deletion,' which is a clear when-to-use tip for safe operation. It doesn't mention alternatives like 'k8s_apply' for updates or specify when not to use this tool, so it's not a full 5.

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