affiliate_hotmart_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 the return type (an array of Programme records) and the scope (joined vs available), but it does not mention pagination behavior, authentication requirements, or any side effects. For a read-only list tool, this is adequate but lacks depth.

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?

Three sentences with clear front-loading: purpose first, then example queries, then return type and related tools. Every sentence adds distinct value 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?

The description covers core purpose and usage examples but completely omits parameter semantics, pagination behavior, and output details (no output schema). With 6 filter parameters and no schema descriptions, the tool is under-specified for correct invocation.

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 coverage is 0% — none of the 6 parameters (limit, cursor, offset, search, status, categories) are described in the schema, and the description does not explain any of them. An agent would have no idea how to use filters like status or categories, leaving a significant gap.

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 'List' and the specific resource 'affiliate programmes the publisher has joined on Hotmart (or which are available to join)', distinguishing it from other networks' list_programmes tools and from get_programme. It also provides concrete example queries that reinforce the purpose.

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?

It explicitly says when to use the tool with example user queries ('which merchants am I working with?', 'what programmes do I have on Hotmart?') and mentions alternatives: get_programme for drill-down and list_transactions for activity. This gives clear guidance on when not to use it.

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