affiliate_tolt_list_programmes

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

No annotations are provided, so the description carries the full burden. It discloses the return type (array of Programme records) and the joined/available scope, but omits details like authentication requirements, pagination behavior, or any side effects. This is a read operation, but more explicit safety disclosure would be helpful.

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 three sentences, front-loaded with the core purpose, followed by usage examples and return type/pairing. Every sentence contributes useful information with no redundancy.

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?

With 7 parameters and no output schema, the description is incomplete. It fails to explain parameter semantics, filter behavior, or how the joined/available distinction is represented. The tool requires more context for effective use.

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 does not mention any of the 7 parameters. The required 'brand' parameter is left completely unexplained, leaving the agent without guidance on how to populate filters like status, search, or categories.

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 it lists Tolt affiliate programmes, specifying a verb ('List') and resource ('affiliate programmes'). It distinguishes from sibling list_programmes tools by naming the network (Tolt) and gives example user queries to clarify scope.

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 when-to-use triggers with example phrasings and mentions complementary tools (get_programme, list_transactions). However, it does not explicitly state when not to use it or contrast with other networks' list_programmes tools.

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