ebay_get_custom_policy

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

The description only states 'Get' without disclosing any behavioral traits such as required permissions, potential side effects, or error scenarios. With no annotations provided, the description fails to convey essential safety or operational context beyond the basic read operation.

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 concise: one sentence that front-loads the purpose ('Get a specific custom policy by ID'). No wasted words; every part contributes to clarity.

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?

The tool has no output schema, so the description should explain what a custom policy contains or its format. It does not, leaving agents uncertain about the return value. Additionally, context about how custom policies differ from other policies is missing, which is important given the many sibling tools.

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% as the single parameter 'customPolicyId' is described in the schema. The description adds no additional meaning beyond what the schema already provides, so it meets the baseline of 3.

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 specifies the action ('Get') and the resource ('a specific custom policy by ID'), using a specific verb and resource that distinguishes this tool from siblings like 'ebay_get_custom_policies' (plural) and 'ebay_create_custom_policy'.

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 alternative policy retrieval tools (e.g., ebay_get_fulfillment_policy, ebay_get_return_policy). The context does not explain what a custom policy is or how to decide which getter to use.

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