keap_get_affiliate_summary

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

With no annotations, the description must convey behavioral traits, but it only says 'Get summary stats for an affiliate'. It does not disclose whether the tool is read-only, requires special permissions, or what the 'summary stats' entail, leaving the agent uncertain.

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 sentence, very concise. However, it lacks additional context that could be added without verbosity, such as the scope of the summary. It earns a middle score for being succinct but not thorough.

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?

Given the simplicity (1 param, no output schema, no annotations), the description is incomplete. It fails to specify what the summary includes or how the returned data is structured, which could lead to incorrect tool selection among sibling affiliate tools.

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?

The schema has one parameter 'affiliate_id' with a description, achieving 100% coverage. The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate since the description doesn't compensate or enhance parameter understanding.

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 'Get summary stats for an affiliate' clearly states the verb and resource. Among siblings like keap_get_affiliate, keap_get_affiliate_clawbacks, etc., the specification of 'summary stats' distinguishes this tool from those that retrieve specific details.

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 keap_get_affiliate or keap_get_affiliate_commissions. The description lacks context about what scenarios warrant a summary vs detailed data.

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