ebay_get_listing_violations_summary

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

With no annotations, the description bears full responsibility for behavioral disclosure. It fails to explain what 'summary' entails, whether the operation is read-only, what permissions are required, or the type of data returned. The minimal text does not compensate for missing 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?

The description is very concise (one sentence), but this brevity sacrifices critical information. It is front-loaded with the main action but fails to elaborate on usage or behavior, making it less helpful.

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 lack of output schema and minimal parameter description, the description is incomplete. It does not clarify what constitutes a violation, how the summary is structured, or how to use the complianceType filter. Sibling tools exist for details, but no relationship is mentioned.

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?

The input schema has one optional parameter 'complianceType' with a description 'Type of compliance violation'. Since schema coverage is 100%, the description adds no extra meaning beyond the schema. Baseline 3 is appropriate.

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 'Get summary of listing violations' clearly states the action (get summary) and the resource (listing violations). The tool's name reinforces this, distinguishing it from the sibling 'ebay_get_listing_violations' which likely returns full details, though the description does not explicitly differentiate.

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?

No guidance is provided on when to use this tool versus alternatives like 'ebay_get_listing_violations'. The description lacks any mention of use cases, prerequisites, or scenarios where the summary is preferred over detailed violations.

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