Listing Bureau - Amazon Organic Ranking

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

While annotations declare readOnlyHint=true, the description adds valuable behavioral context: 'Returns empty object if no plan is active.' This specific edge-case behavior helps the agent interpret responses correctly without trial and error.

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?

Two sentences with zero waste. First sentence front-loads the core purpose; second sentence provides the critical edge-case behavior. No redundant or filler content.

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?

Adequate for a simple getter with no output schema. Covers the success case (get rates) and edge case (empty object). Could be improved by briefly describing the structure of returned rate data (e.g., whether it's a tiered pricing object or flat rate), but sufficient for tool selection.

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?

Zero parameters with 100% schema coverage (empty object). Description correctly focuses on behavior rather than inventing parameter documentation. Baseline 4 achieved as no parameters require semantic explanation.

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?

Specific verb 'Get' plus precise resource 'Listing Bureau service pricing rates' clearly defines scope. Distinct from sibling lb_estimate_cost (which calculates specific costs) and lb_account_get_subscription (which gets subscription status) by focusing on base pricing rates.

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?

Lacks explicit when-to-use guidance contrasting with lb_estimate_cost. Agent must infer this retrieves rate cards/pricing tiers while lb_estimate_cost calculates projected costs. No prerequisites or conditions mentioned beyond the no-plan edge case.

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