sellfox_ads_sb_creatives

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The phrase '基础数据' implies a read-like operation, but it does not explicitly state whether the tool is read-only, destructive, or requires specific authentication. No side effects, rate limits, or return behavior are mentioned.

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 a single short sentence, which is concise but at the expense of clarity and utility. It fails to convey the core action or value, making it insufficiently informative for an effective tool definition.

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 4 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what data is returned, how to filter or interpret results, or how to differentiate from a large set of sibling tools. The context provided by the 30+ sibling tools amplifies the need for clearer guidance.

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 100% with all parameters having Chinese descriptions (e.g., '状态过滤' for state filter). The tool description itself does not add any parameter-level detail beyond the schema, so it provides no additional semantic value. Baseline score of 3 is appropriate given full schema coverage.

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 is a noun phrase 'SB广告产品(创意)基础数据' (SB advertising product creative basic data), lacking a verb to indicate the action (e.g., retrieve, list). It vaguely hints at getting basic data for SB ad creatives but does not clearly specify what the tool does, nor does it distinguish from similar sibling tools like sellfox_ads_sb_campaigns or sellfox_ads_sd_creatives.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or scenarios where this tool is appropriate, leaving the agent without decision-support for tool selection among many sibling tools.

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