page_estimate

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and it does well: it discloses the estimation method (rendered page marks and explicit breaks take precedence, word-count model as fallback) and warns that every value is `estimated: true`. It doesn't note precision limits or pagination behavior, but the methodology disclosure is the key behavioral fact.

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 tight sentences, front-loaded with the output subject and followed by the method caveat. Nothing is padded.

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?

For a 5-param read-only tool with no output schema, the description covers what is returned, how it is computed, and its reliability caveat. Cursor/limit semantics are left entirely to the schema, which documents them, so nothing critical 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 100% with example addresses and limits already documented, so the baseline is 3. The description's parenthetical echoes the `at`/`by` distinction but adds no syntax or format detail beyond the schema.

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 resource (page position of paragraphs) and scope ('each paragraph (or of one)'), enough to distinguish it from paragraphs_list or stats. It reads slightly as a field label rather than a full verb, but the intent is unambiguous.

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 named, despite siblings like paragraphs_list, stats, and locate being plausible substitutes. The 'or of one' hint implies the `at` filter but never says when to prefer the single-paragraph mode.

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