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 states the tool lists deployments with specific statuses but doesn't cover critical aspects like whether it's read-only, requires permissions, handles errors, or returns structured data. This leaves significant gaps for a Kubernetes tool.

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, efficient sentence that front-loads the core action ('List deployments') and includes key details without waste. Every word contributes directly to understanding the tool's function.

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 Kubernetes tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error handling, return format, and integration context, making it incomplete for safe and effective use by an AI agent.

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 input schema has 100% description coverage, fully documenting the two parameters ('namespace' and 'allNamespaces'). The description adds no parameter-specific information beyond what's in the schema, so it meets the baseline score of 3 without compensating or adding extra value.

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 ('List') and resource ('deployments') with specific status fields mentioned ('replicas, available, and ready status'), making the purpose unambiguous. However, it doesn't differentiate from sibling k8s tools like 'k8s_get_pods' beyond the resource type, so it doesn't fully distinguish operational 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?

No guidance is provided on when to use this tool versus alternatives like 'k8s_get_pods' or 'k8s_describe', nor does it mention prerequisites such as cluster access or namespace defaults. The description lacks explicit usage context or exclusions.

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