Miyabi MCP Bundle

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. 'Export' implies a read operation that generates output files, but it doesn't specify whether this requires permissions, what happens to existing data, rate limits, or what the output looks like. The description adds minimal behavioral context beyond the basic action.

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 at just three words, with no wasted language. However, this brevity comes at the cost of completeness - it's arguably too terse for a tool that likely has important behavioral characteristics that need explanation.

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 metrics export tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what metrics are exported, from what source, in what structure, with what permissions, or how the output is delivered. Given the complexity implied by sibling metrics tools, this leaves significant gaps.

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%, but there's only one parameter with an enum (format: json/csv). The description mentions 'JSON/CSV' which aligns with the enum values, adding some semantic meaning. However, it doesn't explain what the format parameter controls, default behavior, or other contextual details about parameter usage.

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 'Export metrics JSON/CSV' restates the tool name 'metrics_export' with added format options, making it tautological. It specifies the action 'export' and resource 'metrics' but lacks specificity about what metrics are exported or from where, and doesn't distinguish from sibling tools like metrics_aggregate, metrics_collect, metrics_query, or society_metrics_summary.

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. It doesn't mention prerequisites, context, or exclusions, leaving the agent with no information about appropriate usage scenarios compared to related metrics tools.

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