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

Annotations include readOnlyHint=true, consistent with the description's 'list' action. The description adds value by mentioning optional filtering but does not disclose pagination or what the response looks like. Given annotations cover the read-only nature, the description is adequate but not exhaustive.

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 concise sentences: first states the core function and optional filters, second provides the API endpoint. No redundancy or unnecessary words. The front-loading is effective.

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?

The tool has 4 parameters with full schema descriptions but no output schema. The description implies the response is a list of document references but does not specify structure or mention pagination. Given the tool's simplicity and the presence of sibling tools for related actions, the description is nearly complete for a list operation.

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% with descriptions for each parameter. The description groups the parameters conceptually (date range and content search) and highlights their optionality, adding context beyond the schema. This helps the agent understand how to combine filters effectively.

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 clearly states the verb 'list', the resource 'document references currently available for a Patient', and optional filters (date range and content search). It also includes the API endpoint, which distinguishes it from sibling tools like 'metriport_start_document_query' that perform different actions.

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 does not provide guidance on when to use this tool versus alternatives. For instance, it does not clarify that this tool lists already available documents, while 'metriport_start_document_query' is for initiating a query to fetch new documents. Without such guidance, an agent may misuse the tool.

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