keap_add_contact_to_sequence

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

With no annotations, the description carries the full burden. It only states 'Add a contact' but does not disclose whether adding is idempotent, if there are side effects, error conditions, or what happens if the contact is already in the sequence. The description adds minimal value 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, which is compact but lacks necessary detail. It is not front-loaded with critical context. While concise, it sacrifices completeness.

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 of the tool (2 params, no output schema), the description could still benefit from explaining return values, potential errors, or idempotency. The sibling tools suggest alternatives but the description does not clarify how this tool fits. It leaves the agent underinformed.

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 baseline is 3. The description does not add any extra meaning to the parameters beyond 'Contact ID' and 'Sequence ID'. It does not explain format, constraints, or how to obtain these IDs.

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 (Add) and the target (contact to a campaign sequence). It distinguishes from siblings like keap_add_contact_to_campaign and keap_remove_contact_from_sequence by specifying the resource (sequence) and the operation (add). However, it lacks nuance like explaining that a sequence is part of a campaign.

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 such as keap_add_contact_to_campaign. There are no prerequisites, exclusions, or context hints. The agent is left to infer usage from the name alone.

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