docx.find

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full behavioral disclosure burden. 'Find text in document' only names the operation and does not state whether it is read-only, whether it modifies anything, whether it returns match locations, or what its case-sensitivity rules are.

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 a single, concise phrase with no filler words and is naturally front-loaded. It is not bloated, though the brevity contributes to under-specification.

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, no output schema, and no parameter documentation, 'Find text in document' is too minimal to support confident invocation. The description does not explain whether a document must already be open, whether a query is required, what the return structure is, or how results are ordered.

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 input schema has zero properties, so there are no parameter semantics to describe and the '0 params equals baseline 4' rule applies. The description adds no parameter details, but the ambiguity about how a search term is supplied is arguably a broader specification gap than a parameter-semantics gap.

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 names a definite action ('find') and a resource ('text in document'), so an agent can infer this is a text-search operation. However, it does not differentiate it from sibling text tools like get_text or replace_text, nor does it say what the output of the find operation is.

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 is provided, and there are no references to alternatives. The sibling list includes many text-related operations, but the description never clarifies whether to prefer docx.find over docx.get_text or docx.replace_text.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.