ebay_leave_feedback_for_buyer

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

With no annotations, the description must disclose behavioral traits. It only says 'Leave feedback', implying a write operation, but omits details like idempotency, effects on seller/buyer ratings, or that feedback can only be left once per transaction. Insufficient for safe invocation.

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?

The description is extremely short (4 words), which is concise but lacks structure. It fails to provide any auxiliary information that would aid an agent, making it under-specified rather than optimally concise.

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 tool has one nested parameter and no output schema, the description leaves out critical context: feedback prerequisites, the fact that orderLineItemId must reference a valid transaction, and what happens on success/failure. Not complete enough for reliable use.

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 description coverage is 100% but the description adds no extra meaning beyond the bare field names and a generic 'Feedback details including rating and comment'. It does not explain the role of each nested property (rating, feedbackText, orderLineItemId) or constraints like rating enum values.

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 states the verb 'Leave' and resource 'feedback for a buyer', making the basic purpose clear. However, it is vague and does not distinguish from sibling tools like ebay_respond_to_feedback or ebay_get_feedback, which have overlapping domains.

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?

There is no guidance on when to use this tool versus alternatives, no context about prerequisites (e.g., need an order) or exclusions. The description provides no usage direction.

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