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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior. The description adds useful non-annotation behavior: ordering is newest first, company documents are excluded, and pagination is explained in detail including nextCursor presence/absence and how to continue.

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 definition is front-loaded with scope and ordering, then gives only the necessary exclusion and pagination details. Every sentence carries operational value, and the continuation instruction is clear without unnecessary 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?

For a paginated list tool with full schema coverage, annotations, and an output schema, the description is complete enough to call correctly. It covers scope, ordering, exclusion, and pagination behavior, leaving return-value details to the output schema.

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%, so lang, limit, and cursor are already documented in the schema. The description reiterates cursor continuation but does not add meaning beyond the schema for any parameter, which fits the baseline of 3.

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 specifies the resource and scope: the independent source library, ordered newest first, excluding company-supplied documents. It is clear enough to distinguish this from a general document search, but it does not name the sibling tools an agent should use for company documents or targeted lookups.

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?

It implies this is the browsing/list tool for the independent source library and explicitly excludes company-supplied documents. However, it does not name an alternative such as search_documents for those excluded documents, so routing guidance is only partial.

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