sellfox_ads_sd_creatives

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

No annotations exist, so the description must fully disclose behavior. It only says 'basic data,' which does not indicate whether the tool is read-only, what data is returned, pagination, authentication needs, or any side effects. This is a critical gap for a data retrieval tool.

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 incomplete sentence that is too vague to be useful. Conciseness is good, but it sacrifices essential information. Every sentence should add value; this one does not adequately describe the tool's function.

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 many sibling tools, the description is extremely incomplete. It fails to explain return format, usage context, or how filters work. The minimal information leaves an agent with insufficient guidance to select or invoke correctly.

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%, so each parameter has a description in the schema. The tool description adds no information about parameters beyond the schema, meeting the baseline of 3 as per guidelines. However, it could have integrated parameter context (e.g., 'state filters creatives by status').

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 'SD广告创意基础数据。' is a noun phrase stating 'SD advertising creative basic data.' It lacks a verb indicating the action (e.g., retrieve, list, get), making the purpose vague. Among siblings like sellfox_ads_sd_campaigns and sellfox_ads_sd_ad_groups, this description does not differentiate what 'creatives' means or how this tool is distinct.

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 provided on when to use this tool versus alternatives. With many sibling tools for SD ads (campaigns, ad groups, etc.), the description should specify scenarios such as 'Use this to view ad creatives for a campaign' or note prerequisites. None are present.

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