Listing Bureau - Amazon Organic Ranking

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

Annotations declare readOnlyHint=true, confirming safe read behavior. The description adds valuable behavioral context by enumerating the specific data fields returned (email, name, status, balance), compensating for the missing output schema. It does not mention rate limits or caching, but the core return structure is disclosed.

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 sentence with no wasted words. The parenthetical field list efficiently conveys the return payload. Information is front-loaded and dense.

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 no output schema exists, the description adequately compensates by listing the four key fields returned. For a simple zero-parameter read operation with readOnlyHint annotation, this covers the essential behavioral contract without needing exhaustive detail.

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 exist in the input schema, establishing a baseline of 4. No parameter documentation is required or provided.

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 specific verb 'Get' and resource 'Listing Bureau account info' plus lists exact fields returned (email, name, account status, wallet balance). Distinguishes from siblings like lb_account_get_subscription and lb_account_update_profile by scope, though it doesn't clarify the overlap with lb_wallet_get_balance.

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?

Provides no guidance on when to use this tool versus the specialized siblings like lb_wallet_get_balance (which also returns wallet data) or lb_account_get_subscription. No prerequisites or conditional usage advice is included.

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