keap_list_subscriptions

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does not mention that the operation is read-only, whether pagination is used (though the schema has a limit parameter), or any rate limits. The description is too brief to compensate for missing 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 concise sentence that gets to the point. It is front-loaded with the core action. However, it could be improved by briefly listing the filter options or mentioning pagination, but the current length is still effective for a simple tool.

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 no output schema and all parameters are optional, the description fails to explain the response format or default behavior (e.g., pagination limit). It does not tell the user what to expect from the list or how to handle large datasets.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond 'filtering'; it does not clarify how filters interact (e.g., AND logic) or provide format details. The schema already documents each parameter sufficiently.

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 tool lists subscriptions and supports filtering. The verb 'List' matches the tool's naming convention, and 'subscriptions' is a specific resource. However, it does not explicitly differentiate from other list tools like keap_list_contacts or keap_list_products, which may also support filtering.

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 (e.g., keap_get_subscription for a single subscription). There are no usage examples or context about prerequisites (e.g., need a contact ID for filtering). The description simply states functionality without directing the user.

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