getDocumentList

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention pagination, filtering, return format, authentication requirements, or whether it returns metadata rather than file content. The word 'list' implies a read operation, but nothing further is disclosed.

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 description is a single sentence with no wasted words, making it concise. However, it is too terse for a tool with 7 parameters and no output schema, and it lacks structural elements like usage context or parameter overview.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description is severely incomplete. It provides only a one-line summary and fails to explain return values, filtering, sorting, pagination, or any behavioral nuances, making it inadequate for an agent to use correctly.

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?

The description adds no information about the 7 parameters. The schema provides descriptions for 4 of them (beginTime, endTime, category, serviceName) but leaves sort, order, and locale undocumented. With 57% schema coverage, the description should compensate but does not mention any parameters at all.

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 says 'Метод предоставляет список документов продавца' (Method provides a list of seller's documents), which clearly states the verb (provides) and resource (list of documents). It is not a tautology and distinguishes from siblings like downloadDocumentsAll or getDocumentCategories, though it does not explicitly differentiate from them.

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?

There is no guidance on when to use this tool versus alternatives. The description only states what the method does, without mentioning use cases, exclusions, or comparisons to sibling tools like downloadDocumentsAll or getReportDetailByPeriod.

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