Listing Bureau - Amazon Organic Ranking

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

Annotations declare readOnlyHint=true; description adds valuable behavioral context beyond this: default sort order (newest first), pagination model, and specific response fields included (order status, campaign, region, issue report status). No contradictions with annotations.

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 establishes operation and key behaviors (pagination, sorting), second previews response payload. Information is front-loaded and every clause 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?

For a simple 2-parameter list operation, description adequately compensates for missing output schema by enumerating returned fields (status, campaign, region, issue report status). Combined with readOnly annotation and full schema coverage, provides sufficient context for 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?

Schema has 100% description coverage (default values, min/max constraints), so baseline applies. Description mentions 'paginated' conceptually but doesn't add parameter-specific semantics (e.g., cursor vs offset pagination) beyond what schema already documents.

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?

Clear verb 'List' + resource 'Listing Bureau orders' with scope indicators 'paginated, newest first' that distinguish it from sibling lb_orders_get (singular retrieval) and lb_orders_report_issue (mutation). Plural 'orders' and pagination signal bulk listing vs individual fetch.

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 implied usage through 'paginated' and response field preview (status, campaign, region), indicating when you need order overviews. However, lacks explicit guidance on when to use lb_orders_get for specific order retrieval instead, or filtering limitations.

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