keap_list_transactions

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

With no annotations, the description must disclose behavioral traits. It only says 'List', implying read-only, but does not confirm idempotency, authentication requirements, rate limits, or what happens to the system. The brief phrase fails to provide transparency beyond the obvious.

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 sentence, which is efficient. However, it may be too minimal, sacrificing clarity and completeness. Every word does earn its place, but more context would be beneficial.

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 lack of output schema and the presence of 5 parameters, the description is incomplete. It does not explain the return format, pagination behavior, or how filtering affects results. The agent needs more context to use the tool effectively.

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 input schema has 100% coverage, so the baseline is 3. The description adds no extra meaning beyond the schema parameter descriptions, merely stating 'with filtering'. It does not explain how the parameters interact or provide usage examples.

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 action 'List transactions' and the capability 'with filtering'. It is specific about the resource (transactions). However, it does not differentiate from sibling list tools like keap_list_orders or keap_list_order_transactions, leaving ambiguity about what type of transactions are included.

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 guidelines are provided on when to use this tool versus alternatives. There are several sibling list tools (e.g., keap_list_orders, keap_list_order_transactions) but this description gives no comparative context or exclusions, forcing the agent to guess.

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