keap_list_orders

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states the tool lists orders with filtering, but does not mention whether it is read-only, pagination details, rate limits, or other behavioral traits. The agent gains minimal behavioral insight beyond the tool name.

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, making it concise. However, it is overly brief given the complexity of the tool (7 parameters, no output schema). It sacrifices informativeness for brevity, resulting in a minimally viable but not helpful description.

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 tool has 7 optional parameters, no output schema, and no annotations, the description is incomplete. It does not explain output format, pagination behavior (e.g., default limit, offset usage), or how it relates to sibling tools like keap_get_order or keap_list_order_transactions. Agents would need to infer crucial details.

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 all parameters are documented in the schema. The description adds no additional meaning beyond 'with filtering', which is already implied by the parameter names and descriptions. Baseline 3 is appropriate as the description does not need to compensate but also adds no extra value.

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 orders with filtering' clearly indicates the action (list) and resource (orders), and implies filtering capability. However, it does not specify the scope (e.g., all orders or contact-specific) and could be more distinct from sibling tools like keap_get_order or keap_list_order_transactions.

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 explicit guidance on when to use this tool versus alternatives like keap_get_order (for single order) or keap_list_order_transactions. The description does not mention use cases, prerequisites, or 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.