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

Annotations already declare readOnlyHint=true and the description simply repeats 'Read-only', earning no extra credit there. It does add the underlying GraphQL query shape, which is useful for debugging, but it omits behavioral traits such as pagination defaults/limits and what a page of results contains. Notably the GraphQL signature lists should_paginate, a parameter absent from the input schema, which an agent cannot act on.

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?

Three short sentences with the scoping behavior front-loaded and no filler. The trailing GraphQL query restatement is mildly redundant with the schema but short enough to be defensible.

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?

There is no output schema, yet the description says nothing about the return shape (what a document record contains) or pagination totals, and it does not resolve the extra should_paginate parameter appearing only in the GraphQL string. For a simple read-only list tool keyed off annotations this is adequate but not complete.

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 offset, page_size, keywords and viewable_user_id are already fully documented in the schema; that sets the baseline at 3. The description names viewable_user_id and keywords but adds no syntax, format, or constraint detail beyond what the schema already provides.

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+resource (list documents) and adds the two optional scoping modes (patient via viewable_user_id, or keyword search), which is more than a restatement of the title. It does not explicitly differentiate itself from the many sibling list_* tools, though none of them overlap on the document resource, so confusion risk is low.

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 description implies usage (scope to a patient, or search by keyword) but never states when to use this tool versus an alternative, nor any prerequisites such as required permissions or needing a patient context. For a zero-required-parameter list tool the implied context is workable but thin.

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