ebay_get_fulfillment_policies

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

No annotations provided, so the description carries full burden. It only states the function and scopes, omitting behavioral traits like pagination, return format (list?), rate limits, or error handling. For a read operation, this 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 concise with two sentences, front-loading the purpose. It is efficient, though it could include more relevant details without losing conciseness.

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 tool has one parameter and no output schema, the description is minimally complete but lacks guidance on output format (e.g., returns a list) and pagination. For a list endpoint, this information is crucial.

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 description coverage is 100% (parameter 'marketplaceId' has a description). The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate as schema covers the parameter adequately.

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' and resource 'fulfillment policies'. However, it does not distinguish from the sibling tool 'ebay_get_fulfillment_policy' (singular), which likely retrieves a single policy. The plural form implies multiple, but explicit clarification would improve clarity.

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 OAuth scope requirements but offers no guidance on when to use this tool versus alternatives like 'ebay_get_fulfillment_policy' or 'ebay_get_fulfillment_policy_by_name'. It lacks explicit when/when-not/alternatives.

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