affiliate_ebay_list_programmes

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

No annotations are provided, so the description carries the burden. It reveals the tool is read-oriented by using 'List' and states it returns an array of Programme records. However, it does not disclose authentication requirements, pagination behavior, rate limits, or other side-effect information that an agent might need.

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 front-loaded with the core purpose, followed by concrete usage examples and related-tool references. It is three concise sentences with no filler or redundant restatement of the tool name.

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?

Covers the essential purpose, scope, return type, and common usage contexts, which is good for a simple list tool. However, it omits parameter semantics and pagination expectations, and with no output schema or annotations, the overall picture is incomplete for an agent needing to invoke it with the right filters.

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?

Six parameters exist with 0% schema description coverage, and the description does not explain limit, cursor, offset, search, status, or categories. The property names offer some self-evident meaning, but the description adds no value to parameter understanding, failing to compensate for the lack of schema documentation.

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 tool lists affiliate programmes on eBay Partner Network, specifying scope ('publisher has joined' or 'available to join'). It distinguishes from sibling list_programmes tools by explicitly naming the network and giving example user queries.

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?

Provides explicit 'Use this when' guidance with realistic user phrases and names related tools (get_programme, list_transactions) for drill-down and activity. It lacks explicit when-not-to-use instructions for other network-specific list_programmes tools, but the context is clear.

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