sellfox_settlement_detail

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

With no annotations present, the description carries the full burden of behavioral disclosure. It only says 'query settlement details', omitting any information about data freshness, pagination, rate limits, or whether it only returns non-deleted entries. The description is insufficient for an agent to understand the tool's behavior.

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 extremely concise, containing only a single phrase. While it efficiently conveys the core purpose, it could be expanded with minimal effort to include key behavior or usage hints without becoming verbose.

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 has 19 parameters and no output schema or annotations, the description is too sparse. It fails to summarize the tool's scope, return type, or any critical interactions between parameters. A more informative description is needed for an agent to use this tool effectively.

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%, so the schema already documents all 19 parameters with descriptions. The tool description adds no additional parameter information beyond the schema, which is adequate but not exceptional. A baseline score of 3 is appropriate.

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 '查询结算明细(V2)' clearly states the action (query) and resource (settlement details). It is specific, but does not explicitly differentiate from sibling tools like sellfox_settlement_summary, which may cause ambiguity. However, the name and context strongly imply it returns detailed records rather than summaries.

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?

No usage guidance is provided. The description does not specify when to use this tool versus alternatives, nor does it indicate any prerequisites or constraints. The agent receives no help in deciding whether this is the appropriate tool.

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