get_member_activity

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

Discloses necessary authentication (API key), rate limits (max 10 concurrent), idempotency (read-only, safe to retry), and error behavior (404 if member not in audience). No annotations to contradict.

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?

Concise yet comprehensive; each sentence serves a purpose. Structure is logical: purpose, sibling differentiation, behavioral notes, parameter docs, return format. No wasted words.

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?

Covers all necessary aspects: functionality, usage context, prerequisites, parameter details, error handling, and return format. Output schema exists so return explanation is adequate.

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 0% schema description coverage, the description fully details each parameter: format of list_id (10-char alphanumeric, obtain from list_audiences), email_address constraint (must exist), count range and default. Adds significant value beyond schema.

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 verb 'Retrieve' and resource 'member's email interaction history' with specifics (opens, clicks, bounces) and distinguishes from sibling tools (get_member_events, get_member_tags).

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?

Explicitly states when to use (email actions only), provides alternatives (get_member_events, get_member_tags), a prerequisite (search_members to find audience), and mentions that it is read-only and safe to retry.

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