sellfox_ads_sb_ad_group_hourly

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

No annotations exist, so the description must communicate behavior. It implies a read-only report but lacks details on data freshness, pagination, rate limits, or whether it is destructive. The minimal description does not compensate for the lack of annotations.

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 overly minimal. It lacks front-loaded key information and does not earn its place beyond stating the obvious.

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 complexity of a report tool with many siblings and no output schema, the description is incomplete. It does not specify what data the report returns (e.g., metrics, dimensions), leaving the agent without essential context for correct invocation.

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%, and each parameter has a Chinese description that explains its meaning (e.g., shopId, reportDate with format and range). The description adds no additional parameter semantics beyond what the schema already provides.

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 states the tool provides an hourly report for SB ad groups, which is a specific resource and action. However, it does not differentiate from sibling tools like sellfox_ads_sb_campaign_hourly or sellfox_ads_sp_ad_group_hourly.

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. There is no mention of prerequisites, when-not to use, or context for selection.

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