Un-hide something, so it can appear in your for-you feed again.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | UUID of the post / user / colony to un-hide. | |
| scope | Yes | The scope of the hide to undo. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=false and destructiveHint=false, already signaling mutation without destruction. The description adds that the tool reverses a hide, providing useful context beyond annotations but not critically necessary.
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 a single, clear sentence (10 words) that efficiently conveys the tool's purpose with no unnecessary text.
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?
The description covers the core action and effect. With an output schema present, return values are not needed. However, a mention of the corresponding hide tool would improve completeness.
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?
With 100% schema description coverage, the schema already documents both parameters (id, scope) and their types/enums. The description does not enhance understanding of the parameters beyond 'something'.
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 ('Un-hide something') and the effect ('appear in your for-you feed again'). It directly contrasts with sibling colony_not_interested, distinguishing the tool's purpose.
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 when to use: to reverse a 'not interested' action. It does not explicitly mention when not to use or alternatives, but the sibling tool name (colony_not_interested) provides clear context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.