ebay_get_site_visibility_policies

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

No annotations are provided, leaving the description as the sole source of behavioral info. The description only says 'Get', implying a read operation, but fails to disclose any traits like authentication needs, rate limits, pagination, or error handling. This is insufficient for a tool with no structured behavioral hints.

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 a single, concise sentence that front-loads the core action. It is appropriately sized given the tool's simplicity, though it could benefit from additional structure like a note on returns or usage.

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?

With no output schema and minimal parameter descriptions, the description fails to explain what the returned policies look like, what 'site visibility' means, or any edge cases. This leaves an agent insufficiently informed about the tool's output and behavior.

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%, so baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions. It does not explain the 'filter' parameter's valid values or behavior, nor does it provide context for the marketplaceId enum. No added value beyond what the schema already provides.

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 it retrieves 'site visibility policies' for a marketplace, combining a specific verb and resource. However, among many sibling tools like ebay_get_category_policies or ebay_get_shipping_policies, it does not differentiate what makes 'site visibility' distinct, so it lacks sibling differentiation.

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 no guidance on when to use this tool versus other policy retrieval tools (e.g., ebay_get_classified_ad_policies, ebay_get_regulatory_policies). It also does not mention any prerequisites or contexts where site visibility policies are relevant.

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