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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: each page is capped at 24,000 characters and the call returns text, page count and document details, which tells the agent how to chunk reads.

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 compact clauses, zero filler. The core action and scope come first, and the return/limit detail follows, so the reader is front-loaded with what matters.

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 a full output schema and rich annotations, the description only needs to carry scope and behavioral quirks, and it does. The one missing piece is routing relative to search_docs, which matters given how many sibling tools operate on documents.

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 both parameters (page, documentId) are already documented in the schema with defaults and bounds. The description's 24,000-character note adds context about page sizing but no new syntax or format details. Baseline 3 applies.

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 and resource ('Reads one page of a document') and adds scope ('shared with the connected Twelfth workspace'), which is enough for an agent to identify it. It does not, however, distinguish itself from the sibling search_docs, which likely also touches documents.

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?

Usage is implied: read a page of a document you already have the id for. There is no explicit when-to-use guidance, no mention of the search_docs alternative, and no statement of prerequisites beyond the implicit 'shared workspace' constraint.

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