affiliate_digistore24_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 discloses that the result includes both joined and available-to-join programmes and returns an array of Programme records. However, it does not mention pagination behavior, authentication requirements, or rate limits, leaving some behavioral context unstated.

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?

Two sentences pack the action, use cases, and related tools without waste. Each sentence adds information relevant for selection and invocation.

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?

For a 6-parameter list tool with no output schema or annotations, the description covers purpose, example trigger phrases, and return type, but omits parameter semantics and detailed behavioral notes, leaving moderate gaps.

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 0% and the description provides no meaning for limit, cursor, offset, search, status, or categories. The agent must infer filter and pagination semantics from parameter names alone, which is insufficient for six parameters.

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 'List affiliate programmes the publisher has joined on Digistore24 (or which are available to join)', giving a specific verb and resource. It distinguishes from sibling tools by mentioning get_programme for drill-down and list_transactions for activity.

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?

Explicitly says 'Use this when the user asks...' with concrete example queries, and notes that it 'pairs naturally with get_programme for drill-down and list_transactions for activity', providing clear usage boundaries and alternatives.

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