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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is carried by structured data. The description adds useful context (Premium requirement, the action model, and the self-documenting 'help' call) but does not disclose reversibility, what remove_all actually destroys, or auth requirements.

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?

Compact and front-loaded: capabilities first, then the action list, then the discovery hint. Every sentence earns its place, though the enumerate-actions line partly duplicates the enum.

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 an action-dispatch tool with a nested free-form params object and no output schema, the description does enough to make the tool usable via the 'help' path and notes the Premium gate. It stops short of explaining the params contract or the destructive scope of remove_all.

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?

With 67% schema coverage and an opaque additionalProperties params object, the description's main contribution is pointing to 'help' for field discovery - but that mechanism is already stated in the schema's params description. The action list merely repeats the enum, so little new meaning is added.

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?

States a clear verb set (add, remove, import) and resource (the member's contacts), and enumerates the exact actions supported. It is distinguishable from the read-only sibling get_contacts, though it never names that sibling to route the agent explicitly.

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?

Usage is only implied by the mutation verbs and the '(Premium)' gating note. It offers a 'help' action for field discovery but gives no when-to-use vs alternatives or prerequisites beyond the tier restriction.

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