ebay_get_fulfillment_policies

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

No annotations are provided, so the description must cover behavioral aspects. It adds the required OAuth scopes, which is helpful for authentication transparency. However, it does not disclose rate limits, pagination, or behavior when no policies exist. Given the absence of annotations, the description is partially informative but insufficient for full behavioral transparency.

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 consists of two succinct sentences: the first states the purpose, the second lists required OAuth scopes. Every sentence is necessary and front-loaded. No wasted words.

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 a simple purpose (list fulfillment policies) but given the presence of siblings like 'ebay_get_fulfillment_policy' and 'ebay_get_fulfillment_policy_by_name', the description could better differentiate. No output schema means the return format is not disclosed. It is adequate but not fully complete for an agent to anticipate all behaviors.

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 100% description coverage for the only parameter 'marketplaceId' with an enum and example. The description adds no extra parameter information beyond what the schema already provides, so the baseline score of 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 clearly states 'Get fulfillment policies for the seller' using a specific verb and resource. The plural 'policies' implies a list operation, distinguishing it from the sibling 'ebay_get_fulfillment_policy' which likely returns a single policy. However, it does not explicitly say 'all' or 'list', leaving slight ambiguity.

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 only provides OAuth scope requirements. It does not explain when to use this tool versus alternatives like 'ebay_get_fulfillment_policy' or 'ebay_get_fulfillment_policy_by_name', nor does it mention prerequisites or use cases.

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