Retrieve a specific eBay fulfillment policy by ID. Use it to review or manage shipping and return settings.
Get a specific fulfillment policy by ID
| Name | Required | Description | Default |
|---|---|---|---|
| fulfillmentPolicyId | Yes | The fulfillment policy ID |
Changes observed during successful MCP inspections.
v1.14.1v1.14.1v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility. However, it does not mention any behavioral traits such as read-only nature, required permissions, or rate limits. The description only indicates a read operation implicitly, which is insufficient.
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 sentence that is concise and front-loaded. Every word serves a purpose, and there is no unnecessary information.
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 no output schema, the description fails to indicate what the tool returns (e.g., the fulfillment policy object). Additionally, there is no mention of error handling or conditions, making it incomplete for a simple retrieval tool.
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 single parameter. The description adds that the policy is identified 'by ID', which aligns with the schema's parameter description. No additional meaning beyond that, so a 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 the verb 'Get', the resource 'fulfillment policy', and the method 'by ID'. It distinguishes itself from sibling tools like ebay_get_fulfillment_policies (list all) and ebay_get_fulfillment_policy_by_name (get by name) by specifying the use of an ID.
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 alternatives. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.