sellfox_ads_sd_product_ads

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

With no annotations, the description fully carries the burden of behavioral disclosure. It only says 'basic data' and does not mention whether the tool is read-only, requires specific permissions, or has any side effects. The behavioral traits are not 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?

Description is extremely concise (one short sentence). However, it is front-loaded and has no wasted words. A longer description with more context would improve structure, but it is not overly 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 4 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, scope (e.g., date range), or any operational constraints. A more complete description is needed.

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 has 100% description coverage for 4 parameters. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema already explains the parameters.

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?

Description states 'SD广告产品基础数据' (SD advertising product basic data), which indicates the resource is product ads for Sponsored Display. However, it does not specify the exact action (e.g., list, get) or what 'basic data' includes, making it somewhat vague. Sibling tools like sellfox_ads_sd_campaigns help distinguish the resource.

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 indicate when to use this tool versus other similar tools (e.g., sellfox_ads_sp_product_ads or sellfox_ads_sd_ad_groups). There are no when-not-to-use or alternative suggestions.

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