Get a list of sales invoices

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

注解已声明readOnlyHint=true、idempotentHint=true和destructiveHint=false，提供了安全画像。描述额外说明返回包含行项目，但没有涉及分页行为细节、权限要求或返回格式。有注解降低标准，描述增加了一些上下文，但未达到更丰富的行为披露。

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?

描述整体简短，但存在冗余：'Get a list of sales invoices'与'Get a paginated list of all sales invoices'重复。'[Sales Invoices] GET /invoices/sales'提供了端点信息，但并非必需。结构上能接受，但不够精炼。

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?

该工具没有输出schema，描述仅说明返回列表和行项目，但未说明分页响应结构或其他可能的输出字段。对于7个参数且全部有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覆盖100%，所有参数都有详细描述（如page、sort、filter等）。描述本身没有额外解释参数，基线3分合理。描述中提到的'line items'补充了返回内容，但对参数语义没有增加价值。

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?

描述明确说明了工具的功能：获取销售发票的列表，并包含行项目。动词'Get'和资源'sales invoices'清晰，与兄弟工具如get_sales_invoice（获取单个发票）和list_purchase_invoices（采购发票）有区分，但未明确指出与这些工具的区别，因此不是最高分。

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?

描述暗示了使用场景（获取所有销售发票的列表），但未提供何时使用此工具与替代工具（如get_sales_invoice或list_salesbook_invoices）的明确指导。没有when/when-not说明，只能从'paginated list of all sales invoices'中推断用途。

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