contacts_add_followers_contact

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

Annotations declare readOnlyHint=false and destructiveHint=false, indicating it is a mutation but not destructive. The description adds no behavioral context beyond that—it doesn't mention effects, idempotency, reversibility, or permissions. It is minimal and adds no value over the 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 extremely concise—two words—but it is under-specified. It lacks the structure needed to convey the intended action and context. It is not merely concise; it is incomplete, making it ineffective for agent selection.

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 simple tool with two parameters and no output schema, the description should at least define the parameters and expected behavior. It provides almost no context about what a 'follower' is, how the operation works, or what outcome to expect. The tool is poorly documented even for a simple operation.

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 descriptions cover only 'contactId' with 'Contact Id'; 'followers' has no description. The description 'Add Followers' does not clarify what 'followers' means (e.g., IDs, emails, usernames) or how they relate to the contact. It fails to compensate for the missing schema documentation.

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 'Add Followers' provides a verb and an object but is ambiguous about the context—it does not explicitly state that it adds followers to a specific contact. The tool name contains 'contact' and the schema has a contactId, but the description alone is vague and does not distinguish this from other add operations. It is not a tautology, but it lacks specificity.

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?

The description gives no guidance on when to use this tool versus alternatives, such as contacts_remove_followers_contact or other contacts_add_* tools. There is no mention of prerequisites, exclusions, or scenarios. No usage context is provided.

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