affiliate_manager_list_affiliates

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context, such as pagination behavior, return format, or filtering semantics. It neither contradicts nor enriches the annotations.

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 a single short phrase, which is concise but under-specified. It provides no useful information beyond the tool name, making it under-specification rather than effective conciseness. Every word is wasted on repetition.

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 8 parameters, no output schema, and a description that only says 'List Affiliates', the tool is severely incomplete. It doesn't mention filtering capabilities, pagination, or any constraints, which is inadequate for an agent to select and invoke it correctly in a large sibling set.

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 only 25% (only limit and locationId have descriptions). The description provides no information about any of the 8 parameters, including query, active, date ranges, campaignId, skip, etc. It fails to compensate for the low schema coverage, leaving most parameters unexplained.

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 'List Affiliates' states the verb and resource, distinguishing it from singular get_affiliate and other list tools. However, it is extremely minimal, essentially repeating the tool name, and gives no scope or filtering context. It is clear but not specific about what is listed.

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?

No guidance is provided on when to use this tool versus alternatives like affiliate_manager_get_affiliate, affiliate_manager_list_commissions, or affiliate_manager_list_payouts. No prerequisites or conditions are mentioned, leaving the agent to infer usage from the name alone.

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