drip_get_subscriber

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

No annotations are provided, so the description carries full burden. It does not disclose what happens if the subscriber is not found, rate limits, authentication needs, or any side effects. For a simple read operation, minimal transparency is provided, leaving agents uninformed about error handling.

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?

A single sentence conveys the tool's purpose without any wasted words. It is efficiently structured and front-loaded with key action and resource.

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 fetch operation with one parameter, the description is somewhat complete, but lacks guidance on response format or behavior when subscriber not found. Since no output schema exists, some description of return value would improve completeness.

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 coverage is 100% and the schema already describes the parameter as 'Subscriber ID or email address'. The description reiterates this ('by ID or email'), adding marginal clarity but no new semantic meaning. Baseline 3 is appropriate.

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?

Description clearly states 'Fetch a specific subscriber by ID or email', specifying the verb (fetch), resource (subscriber), and distinguishing method (by ID or email). This differentiates from sibling tools like drip_list_subscribers (list all) and drip_search_subscribers (search results).

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 implies when to use the tool (when you have a specific ID or email) but provides no explicit guidance on when not to use it or alternatives. No mention of scenario-based selection versus siblings like search or list.

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