direct.hf.bid_sweep_analyze

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

With no annotations, the description carries the full burden. It does disclose the key trait — read-only — and the underlying data source, which is useful. However, it says nothing about output format, cost/rate limits, or how the report is scoped, which are relevant for an analysis step.

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?

Single compact sentence with the verb and data source front-loaded. The 'Human-friendly:' prefix adds little and slightly dilutes the lead, but overall it is efficient.

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?

For a 6-parameter tool with two complex required params, no annotations, and no output schema, the description is thin. It is not required to explain return values, but it omits any guidance on the plan_id/windows inputs or the analysis workflow, leaving the definition only minimally viable.

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 67%, so baseline is 3. The four documented params (max_rows, account_id, direct_client_login, include_per_keyword) are explained in the schema, and the description adds nothing for the undocumented plan_id and windows array, leaving their structure and intent to inference.

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?

States a specific verb (analyze), a specific resource (bid sweep plan), and the data source (Direct keyword performance report). This distinguishes it from siblings like bid_sweep_plan and bid_sweep_run, though it never explicitly names what it does relative to them.

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 when-to-use guidance and no routing to alternatives. With close siblings bid_sweep_plan and bid_sweep_run in the same namespace, the description gives no signal about which stage of the sweep workflow this tool serves.

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