Fetch the original content of a knowledge-base document. Includes distilled summaries for Slack threads and, when requested, a heading-based chunk list to navigate long documents.
문서 원문 조회. Slack 스레드면 증류 결과(distilled)도 포함된다. context=1이면 문서의 청크 목록(헤딩 단위)도 함께 반환한다.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | ||
| document_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses some behavior (Slack thread distilled results, context parameter effect) but does not mention side effects, error handling, permissions, or any constraints. Without annotations, this is moderate transparency.
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, using two clear sentences without extraneous information. It is well-structured and easy to parse.
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 simple two-parameter read tool, the description covers the main functionality and the optional context behavior. It lacks explicit mention of error cases or return format, but given the tool's simplicity, it is fairly complete.
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 context parameter is explained in the description, but document_id is not described. Since the schema has no parameter descriptions, the description partially compensates by explaining context but leaves document_id implicit.
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 it retrieves a document's original text, with specific details about Slack thread distillation and optional chunk list. This distinguishes it from sibling tools like search or list_sources.
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. It only describes what it does, not the context in which it should be selected.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.