add_or_update_member

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

No annotations exist, so the description carries the full transparency burden. It usefully discloses automatic hash computation and the compact vs verbose response behavior, but omits side effects, permissions, or error conditions. This is more than a tautology but still minimal for a mutation tool.

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?

Two sentences front-load the purpose and then give essential behavioral details. Every sentence earns its place with zero fluff or repetition.

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 6-param schema with full descriptions and no output schema, the description covers the core upsert behavior and response format, making it sufficiently complete for typical use. It doesn't cover edge cases or prerequisites, but the schema mitigates that.

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?

The input schema has 100% coverage for all parameters, so the description adds little beyond re-stating the verbose option already documented in the schema. It provides no extra semantic detail about parameters themselves.

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 'Add a new subscriber or update an existing one (upsert)' with a specific verb and resource, and the 'upsert' term uniquely distinguishes it from sibling tools like search_members. It leaves no ambiguity about what the tool does.

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 clearly implies when to use it: for adding or updating subscribers. However, it doesn't explicitly contrast it with alternatives like search_members, so it stops short of explicit when-not and alternative guidance.

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