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. While 'Create a PR review' implies a write/mutation operation, the description doesn't disclose important behavioral traits: required authentication/permissions, whether reviews are immediately submitted or saved as drafts, rate limits, error conditions, or what happens when multiple reviews exist. It mentions the three event types but doesn't explain their implications (e.g., APPROVE might merge the PR).

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 - a single sentence that communicates the core purpose efficiently. Every word earns its place: 'Create a PR review' establishes the action, and listing the three event types provides essential context. There's zero waste or redundancy.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the tool returns (success/failure indicators, review ID, etc.), doesn't cover error conditions or permissions needed, and provides minimal behavioral context. Given the complexity of GitHub review operations and the lack of structured metadata, the description should do more to help an agent understand how to use this tool correctly.

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 100%, so the schema already documents all four parameters thoroughly. The description adds minimal value beyond the schema - it mentions the three event enum values (APPROVE, REQUEST_CHANGES, COMMENT) which are already in the schema, but doesn't explain their semantic differences or provide additional context about parameter interactions. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Create a PR review') and specifies the three possible review types (APPROVE, REQUEST_CHANGES, COMMENT). It distinguishes this from sibling tools like github_add_comment or github_submit_review by focusing specifically on creating reviews rather than general comments or submitting existing reviews. However, it doesn't explicitly differentiate from github_list_pr_reviews, which is a read operation.

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 no guidance on when to use this tool versus alternatives like github_add_comment (for simple comments) or github_submit_review (for submitting existing reviews). It doesn't mention prerequisites (e.g., needing appropriate permissions) or contextual factors like whether this should be used during code review workflows versus general discussion.

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