Removes a comment from a Dooray wiki page by specifying the wiki, page, and comment IDs, helping clean up outdated or unwanted page discussions.
Delete a comment on a wiki page.
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | Yes | Wiki page ID (required) | |
| wikiId | Yes | Wiki ID (required) | |
| commentId | Yes | Comment ID (required) |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that – no note that the operation is irreversible, what permissions are needed, or what happens on failure.
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?
A single front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of omitting any warning an agent would want for a destructive call.
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 destructive, required-3-param tool with no output schema, the description should at minimum flag irreversibility or confirmation expectations. Those are absent, leaving an agent with a mutation that has no behavioral framing.
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% with all three IDs documented and required, so the schema does the heavy lifting. The description adds no meaning about the identifiers or their relationships.
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?
Specific verb+resource ('Delete a comment on a wiki page') that clearly distinguishes it from create/update/get-wiki-page-comment siblings. It never names those alternatives, but the operation type alone is unambiguous.
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 on when to use this versus update-wiki-page-comment or delete-task-comment, and no mention of prerequisites or that the deletion is permanent. The agent must infer all of this from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.