word_find_pageFind which pages contain a specific text in a Word document and list the matches in document order.
List the pages on which a piece of text occurs, in document order.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | ||
| text | Yes | ||
| limit | No |
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| pages | Yes |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must carry the behavioral burden. It mentions document order but omits case sensitivity, match semantics, default path behavior, and how limit affects results.
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?
Single sentence, front-loaded, and free of filler. It communicates the operation and ordering without repetition.
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 annotations, 0% schema descriptions, and three parameters, the definition is too thin for reliable invocation. The output schema covers return shape, but input behavior such as path default, limit pagination, and matching rules is missing.
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 description coverage is 0%, so the description needs to explain path, text, and limit. It only implies the required text parameter and says nothing about optional path or the default limit of 20.
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 states a specific action (list pages) and condition (where text occurs) and adds document order. It is distinguishable from word_page_text, though it does not explicitly name siblings or scope.
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 when-to-use guidance or alternatives are given; the agent must infer that this is for locating pages containing text. It does not say when to prefer word_page_text or other page tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.