communications_subscribe_contact

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool performs a subscription action but doesn't disclose whether this requires specific permissions, if it's idempotent, what happens on success/failure, or any rate limits. 'Subscribe' implies a write operation, but no safety or side effect information is provided.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a tool with a straightforward primary function.

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?

For a mutation tool with 3 parameters (including complex enum-based legal basis parameters), 0% schema description coverage, and no output schema, the description is inadequate. It doesn't explain the subscription mechanism, what 'all email communications' entails, or provide any context about the operation's behavior or expected outcomes.

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%, so the description must compensate but provides no parameter information. It doesn't explain what 'contactId' represents, what the legal basis parameters mean, or why they might be required. The description adds no value beyond what's already in the bare schema structure.

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') and target ('a contact to all email communications'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'communications_update_preferences' or 'communications_update_subscription_status' which might have overlapping functionality.

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 about when to use this tool versus alternatives like 'communications_update_preferences' or 'communications_unsubscribe_contact'. The description doesn't mention prerequisites, constraints, or typical use cases for subscribing contacts to communications.

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