Listing Bureau - Amazon Organic Ranking

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

Annotations indicate readOnlyHint: true, confirming safe read behavior. The description adds valuable behavioral context beyond annotations by warning that the response 'May include a warning if data is temporarily unavailable,' alerting agents to potential degraded states not captured in structured metadata.

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 states core purpose immediately, second adds critical behavioral note about data availability warnings. Appropriate length for a simple read-only getter with no parameters.

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 zero-parameter, read-only tool without an output schema, the description adequately covers the essentials by specifying return content type (credits and USD balance) and potential warning flags. Slightly short of perfect only because it doesn't elaborate on the structure of the balance object or exact currency formatting.

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?

Input schema contains zero parameters. Per calibration rules, zero-parameter tools receive a baseline score of 4. The description correctly requires no additional parameter clarification since no arguments are needed to invoke the tool.

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?

Description uses specific verb 'Get' with clear resource 'Listing Bureau wallet balance' and specifies scope '(credits and USD)'. This clearly distinguishes the tool from siblings like lb_wallet_get_transactions (which retrieves transaction history) and lb_wallet_topup (which adds funds).

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?

While the specificity of 'wallet balance' versus siblings implies usage (retrieve current funds vs. history or adding funds), there is no explicit guidance on when to use this versus alternatives, prerequisites, or conditions that would warrant checking the balance first.

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