Create a quote-with-context anchor for a document range, so the same passage can be found after edits.
Make an anchor (quote with context) for a range, to find the passage again after edits.
| Name | Required | Description | Default |
|---|---|---|---|
| at | Yes | Range inside one paragraph, e.g. p142#a7b2a7b2:10-15, or a whole paragraph or sentence (p142#a7b2a7b2.s3). | |
| doc | Yes | Path to the .docx file. | |
| context | No | Characters of prefix and of suffix to keep. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true already signals no document mutation, lowering the bar. The description adds useful lifetime context ('find the passage again after edits') but does not disclose whether the anchor is persisted to the .docx or returned as a session handle, nor what the resulting anchor looks like.
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 sentence with no filler, front-loading the verb and resource before the rationale. Nothing is redundant.
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?
With no output schema, the description carries the burden of explaining the return value, yet it never says what an anchor is handed back as (ID, quote, opaque token) or how to feed it to anchor_resolve. Otherwise adequate for a 3-parameter 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%, so the baseline is 3. The description touches the 'context' parameter implicitly via 'quote with context', but adds no syntax or format detail beyond the schema's own descriptions of 'at' and 'context'.
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?
States a specific verb+resource ('Make an anchor... for a range') and clarifies what the product is with a parenthetical ('quote with context') plus its purpose. An agent can distinguish it from a generic create, though it does not name the anchor_resolve sibling it pairs with.
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 clause 'to find the passage again after edits' implies the workflow (create before edits, resolve after), giving implied usage. It does not state when to prefer this over find/locate, nor any prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.