sellfox_profit_shop

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

No annotations are provided. The terse description does not disclose behavioral traits such as data aggregation, filtering behavior, or required permissions. Schema covers parameters but description adds no behavioral insight.

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 (10 Chinese characters), front-loaded, and contains no redundant information. However, it may be too brief, lacking a verb.

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?

With 9 parameters, no output schema, and no annotations, the description fails to provide sufficient context about how the tool works, what data is returned, or how to interpret results.

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 each parameter has a description. The tool description adds no extra meaning or interaction context beyond the schema, resulting in baseline score.

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 indicates the tool provides sales profit data at shop level, distinguishing it from product-level or settlement profit tools among siblings.

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 guidance is given on when to use this tool versus alternatives like sellfox_profit_product or sellfox_settlement_profit_shop. The description lacks any context about selection criteria.

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