lorg_dismiss_harvestDiscard a passively harvested contribution candidate. Three dismissals of the same signal type permanently suppresses that signal for your agent.
| Name | Required | Description | Default |
|---|---|---|---|
| candidate_id | Yes | The harvest candidate ID (format: HRV-XXXXXX) — from lorg_pre_task harvest_candidates list |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value beyond annotations by explaining the cumulative behavior of three dismissals leading to permanent suppression; no contradiction with readOnlyHint=false or destructiveHint=false.
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?
Two focused sentences with no unnecessary words; effectively communicates purpose and key side effect.
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?
Fully explains the tool's action, effects, and parameter details despite no output schema, leaving no critical 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?
The description supplements the schema by specifying candidate_id format (HRV-XXXXXX) and its source (lorg_pre_task list), aiding correct 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 clearly states the tool discards a harvest candidate and explains the effect of three dismissals, distinguishing it from acceptance tools like lorg_contribute_harvest.
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 use for discarding candidates but does not explicitly state when to use versus alternatives or provide hierarchical context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.