Expand a whole document by its document_id (returned on search_twin results that carry one). Returns the document summary plus every part in order and the reassembled full text. Use when the user asks to summarise, read, or pull back a complete document rather than a single matching passage.
| Name | Required | Description | Default |
|---|---|---|---|
| document_id | Yes | The document_id from a search_twin result (the source/parent id). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true and destructiveHint=false. Description adds useful behavioral context about the return structure (summary, parts, full text in order), without contradicting annotations.
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 sentences with no wasted words. Front-loaded with the core function, followed by usage guidance. Every sentence is informative and earns its place.
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?
Description fully explains input (document_id from search_twin), what is returned (summary, parts, full text), and usage context. No output schema needed given the simple return structure outlined. Complete for this tool.
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 coverage is 100% with a detailed description of the document_id parameter. The description does not add extra meaning beyond what is already in the schema, so baseline score of 3 is appropriate.
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?
Description clearly states the verb 'expand' and the resource 'document', highlighting that it returns summary, parts, and full text. It distinguishes from siblings like search_twin by specifying the source of document_id.
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?
Explicitly states when to use this tool: when user asks to summarise, read, or pull a complete document, as opposed to a single matching passage. This provides clear guidance and implicitly indicates not to use for passage-level queries.
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.