sellfox_ads_sp_ad_group_hourly

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

No annotations are present, and the description is only a one-line title. It does not disclose any behavioral traits such as read-only nature, side effects, rate limits, or constraints, leaving the agent without critical information.

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 extremely brief (one sentence), but it lacks necessary detail. Being concise is not a virtue when essential information is omitted.

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 (4 parameters, no output schema, no annotations, many siblings), the description is severely incomplete. It fails to explain what the report contains, how to interpret results, or any prerequisites.

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%, with all parameters having descriptions. The tool description adds no additional meaning beyond the schema, so it meets the baseline. However, it does not enhance understanding.

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 clearly states it is an hourly report for SP ad groups. However, it does not explicitly differentiate it from sibling tools like sellfox_ads_sp_campaign_hourly or sellfox_ads_sp_product_hourly, relying on the name for distinction.

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 similar hourly report tools for different levels and types, the lack of usage context makes selection difficult.

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