locate

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that output is paged (one, a range, or the whole document) and enumerates what is returned, which is useful behavioral context, but it says nothing about cost, permissions, or ordering.

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?

It is a single dense sentence with no padding, so it is compact, but the run-on phrasing ('plus a phrase Word's Find meets once (one, a range, or the whole document, paged)') is hard to parse and the key action is not front-loaded.

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?

This is a 7-parameter tool with a nested detection-profile object, an overrides array, and no output schema, yet the description explains none of the structural-detection behavior or the profile knobs. For a tool of this complexity, reliance on schema text alone leaves the agent without a mental model of what it will get.

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 100%, and the nested profile object is thoroughly documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 applies rather than a penalty.

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 does convey a specific output: per-paragraph chapter/scene/page plus a unique anchor phrase, and a Find-matching phrase, paged. But it reads as a list of return values rather than a stated action, and the vague name 'locate' is never tied to a resource. It is distinguishable from siblings only by inference, not by explicit statement.

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?

There is no when-to-use or when-not-to-use guidance at all. Siblings like paragraphs_list, outline, find, and page_estimate overlap heavily with this tool's output, and the description never says which situation selects locate over them.

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