get_shop_statements_tool

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing: no auth/permission requirements, no explanation of pagination despite next_page_token being present, and no note on how time filters interact with 'daily settlement records'. Only the read-only nature of 'Get' is implied.

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 short sentences with the resource named first and the key parameter hint second. Nothing is wasted or buried.

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?

Although an output schema exists (so return values needn't be described), the thin description leaves a 6-parameter tool with 0% schema coverage and no annotations materially under-specified. An agent cannot confidently construct filters or pagination from this definition.

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 description coverage is 0%, so all six parameters are undocumented in both schema and description. The description mentions only seller_name, leaving page_size, create_time_ge/create_time_lt (presumably integer timestamps), payment_status (unknown allowed values), and next_page_token unexplained.

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 gives a specific verb+resource — 'Get TikTok Shop financial statements (daily settlement records)' — which is concrete and clarifies the ambiguous term 'statements' via the parenthetical. It does not, however, differentiate this from the sibling get_shop_transactions_tool, which an agent could easily confuse with financial statements.

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?

'Use seller_name to specify which shop' is parameter guidance, not usage guidance. It never says when to reach for this tool versus get_shop_transactions_tool or get_shop_orders_tool, nor does it state prerequisites or exclusions.

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