Listing Bureau - Amazon Organic Ranking

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

Excellent disclosure beyond annotations. It confirms the destructive nature ('clears any existing per-day schedule'), explains idempotency ('replaces it with uniform values'), documents default behavior ('All omitted fields default to 0'), and discloses regional execution constraints ('lower execution rate outside US').

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?

Three tightly constructed sentences with zero redundancy. Front-loaded with purpose, followed by critical behavioral warning, then operational constraints. Every sentence earns its place.

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 presence of annotations covering safety profiles and 100% schema coverage, the description provides complete domain-specific context including regional restrictions, default behaviors, and the destructive scope—everything needed for safe 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?

While the schema has 100% coverage, the description adds valuable aggregation ('All omitted fields default to 0') and conceptual framing ('uniform daily volumes') that explains the relationship between parameters. It also reinforces regional constraints that affect parameter applicability.

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 opens with a specific verb phrase ('Quick-set uniform daily volumes') and identifies the resource ('Listing Bureau project'). It effectively distinguishes itself from sibling tools like lb_schedule_set (implied by 'Quick-set' and 'uniform' vs detailed/per-day scheduling).

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?

It provides clear exclusion criteria via the WARNING about clearing existing schedules, effectively indicating when NOT to use this tool (when preserving existing per-day schedules is required). However, it stops short of explicitly naming the alternative tool (lb_schedule_set) to use instead.

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