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

With no annotations, the description carries the full burden; it does add two real behavioral facts — that results are paged and page numbers are one-based, and that returned entries are metadata rather than file contents. It omits ordering, default page size behavior, permission requirements, and what happens when company_name is omitted, so meaningful gaps remain.

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?

A single front-loaded sentence with no filler; the pagination constraint appears usefully early. The phrase "no file contents inferred" is slightly awkward and could be stated more directly.

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 three-parameter tool with zero schema description coverage, no annotations, and no output schema, the description should explain parameter behavior, default paging, and the return shape. It covers only page indexing and metadata-only results, which is not enough for an agent to call it confidently in ambiguous cases.

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 0%, so the description must compensate and it only partially does: "one-based pages" clarifies page numbering semantics. It says nothing about page_size or about how the nullable company_name parameter behaves relative to the "selected company" context, leaving two of three parameters undocumented anywhere.

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 ("List the selected company's document store") with enough scope for an agent to know it enumerates documents rather than fetching one. It does not differentiate against siblings like get_document, list_document_folders, or get_document_email_history, so the agent must infer the boundary itself.

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?

The clause "no file contents inferred" implies this is a metadata-listing call and that reading content is a different operation, which is useful implied routing. However, no sibling is named and there is no explicit when-to-use/when-not or prerequisite guidance.

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