paymenter_manage_affiliate

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

No annotations are provided, so the description carries the full behavioral burden. It hints at mutations by listing create/update/delete but never discloses permissions required, reversibility, side effects, or what delete actually removes. This is a substantial gap for a CRUD tool with zero annotation coverage.

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?

A single tight sentence with the resource front-loaded and the operation set appended. No wasted words, though the generic 'manage' verb and redundancy with the enum keep it from being a model of structure.

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 six-parameter multi-action CRUD tool with no annotations and no output schema, the description is thin. It does not explain per-action return values or behavioral differences between list/get and create/update/delete, leaving the agent underequipped to call it correctly.

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 100%, so parameters are fully documented in the schema (code, reward, enabled, user_id, affiliate_id, action). The description adds no meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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?

States a clear verb+resource ('Manage affiliate partner accounts') and enumerates the five operations. It is readily distinguishable from siblings because it is the only affiliate-oriented tool. However, the operation list merely echoes the action enum, so it is clear without being distinctive.

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?

The description gives no when-to-use context, no prerequisites, and no guidance on selecting among the five actions or preferring this over other tools. It only restates the available operations, leaving the agent to infer usage entirely from the schema.

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