Miyabi MCP Bundle

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

No annotations are provided, so the description carries full burden. It mentions 'Check connectivity' which hints at a diagnostic purpose, but fails to disclose critical behavioral traits: whether this is a read-only operation, if it requires special permissions, what format the output takes, or if it has side effects. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 perfectly concise - two brief sentences that communicate the core functionality and a usage hint. Every word earns its place with zero redundancy. The structure is front-loaded with the primary purpose followed by a contextual hint.

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 parameterless tool with no output schema, the description provides adequate basic information about what the tool returns (interfaces with IP, MAC, status) and a usage context. However, without annotations or output schema, it should ideally provide more detail about the return format, potential limitations, or error conditions to be fully complete.

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 tool has 0 parameters with 100% schema description coverage (empty schema). The description appropriately doesn't waste space discussing non-existent parameters. It efficiently focuses on what the tool does rather than parameter details, which is correct for a parameterless tool.

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 ('network interfaces') with specific attributes (IP addresses, MAC, status). It distinguishes from siblings like network_connections or network_listening_ports by focusing on interface enumeration rather than connections or ports. However, it doesn't explicitly differentiate from network_overview or network_stats which might overlap 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 implies usage for checking connectivity ('Check connectivity'), suggesting this tool is appropriate for network diagnostics. However, it provides no explicit guidance on when to choose this tool over alternatives like network_overview or network_stats, nor does it mention prerequisites or exclusions. The guidance is implied rather than explicit.

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