subscribe_contact_to_list

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

No annotations are present, and the description only discloses status parameter meanings. It lacks details on side effects, required permissions, idempotency, or behavior on duplicate actions.

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 extremely concise with two sentences, no fluff, and front-loaded purpose. Every word earns its place.

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?

Despite an output schema being present, the description fails to explain what subscribing entails (e.g., overwrite behavior, constraints). With 0% schema coverage and no annotations, the description is insufficient for complete understanding.

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 0%, and the description only adds meaning for the 'status' parameter (1=subscribed, 2=unsubscribed). The 'contact_id' and 'list_id' parameters remain unexplained.

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 'Subscribe a contact to a list' with a verb and resource. However, the inclusion of status values for 'unsubscribed' introduces ambiguity since the tool name suggests only subscription.

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 siblings like 'unsubscribe_contact_from_list'. The description does not explain appropriate contexts or alternatives.

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