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 but fails to disclose behavioral traits. It does not indicate if this is a read-only operation, what permissions are needed, how data is retrieved, or any side effects. The description is too minimal to inform the agent about the tool's 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 concise with a single sentence, but it is under-specified rather than efficiently informative. While it avoids unnecessary words, it does not provide enough detail to be truly helpful, striking a balance between brevity and insufficiency.

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 tool's complexity (3 parameters, no annotations, no output schema), the description is completely inadequate. It does not explain the purpose, usage, parameters, or expected outcomes, leaving the agent with insufficient information to use the tool effectively in context.

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 description offers no information about the three parameters (id, key, society), and schema description coverage is 0%. Without any parameter details in the description, the agent lacks understanding of what each parameter means or how they interact, failing to compensate for the schema's lack of descriptions.

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 'Get stored context' restates the tool name 'context_get' with minimal elaboration, making it tautological. It specifies the verb 'Get' and resource 'stored context' but lacks detail on what 'context' entails or how it differs from siblings like 'context_list' or 'context_search', leaving the purpose vague.

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 such as 'context_list' or 'context_search'. The description does not mention prerequisites, exclusions, or contextual cues, offering no help for the agent in selecting among sibling tools.

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