lb_orders_report_issue

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

Annotations only show not idempotent. The description adds the limit per order and that retrying on limit error should not occur, which is useful behavioral context beyond 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 short sentences, no wasted words, and the key information is front-loaded. Every sentence adds value.

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 the two parameters are fully described in the schema and the description covers the essential behavior and constraints, it is complete enough for this simple tool without output schema.

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 coverage is 100% with descriptions for both parameters. The description adds the constraint about a maximum of 5 reports per order, which is not in the schema, providing additional semantic context.

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?

The description clearly states 'Report an issue with a Listing Bureau order' which uses a specific verb and resource, distinguishing it from sibling tools like lb_orders_get and lb_orders_list which are for retrieval.

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 description provides explicit guidance: 'Maximum 5 issue reports per order -- do not retry if you receive a limit error.' This tells the agent when to stop, though it doesn't compare to alternatives (there are none obvious).

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