Listing Bureau - Amazon Organic Ranking

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

Annotations declare destructiveHint=true, indicating state mutation, but the description only states 'Generate... URL' which understates the write operation (creating a checkout session). No explanation provided for why this is destructive or what side effects occur.

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. Front-loaded with the core action (Generate Stripe checkout URL) followed by return value description. Every word 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?

Adequate for a single-parameter tool, but gaps remain regarding the destructive annotation and the post-payment flow (e.g., whether balance updates automatically after URL completion). Without output schema, the description adequately covers the return value.

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?

With 100% schema description coverage ('Top-up amount in USD...'), the schema fully documents the parameter. The description adds no additional semantics about the amount parameter beyond what the schema already provides, meeting the baseline.

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 'Generate' combines with explicit resources 'Stripe checkout URL' and 'wallet balance'. The scope (topping up vs viewing) clearly distinguishes it from siblings lb_wallet_get_balance and lb_wallet_get_transactions.

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?

The phrase 'to top up wallet balance' provides implied usage context (use when adding funds), but there is no explicit when/when-not guidance or comparison to sibling tools like lb_wallet_get_balance.

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