get--v3-domain_name-unsubscribes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List all unsubscribes' implies a read-only operation but does not specify pagination, rate limits, authentication needs, or what 'all' entails (e.g., time range, filtering). This leaves significant gaps in understanding the tool's behavior.

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 with a single sentence, 'List all unsubscribes', which is front-loaded and wastes no words. It efficiently conveys the core action, though it may be overly brief for the tool's complexity.

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 complexity (5 parameters, 3 required, no output schema, and no annotations), the description is incomplete. It does not address parameter usage, behavioral traits, or output expectations, making it inadequate for effective tool selection and invocation by an AI agent.

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 5 parameters with 0% description coverage, and the description does not mention any parameters. It fails to add meaning beyond the schema, such as explaining what 'domain_name', 'address', or 'term' represent in the context of listing unsubscribes, which is critical given the low schema coverage.

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 'List all unsubscribes' clearly states the verb ('List') and resource ('unsubscribes'), making the purpose understandable. However, it lacks specificity about scope (e.g., for a domain) and does not distinguish from sibling tools like 'get--v3-domain_name-unsubscribes-address', which appears related but is not differentiated here.

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?

No guidance is provided on when to use this tool versus alternatives, such as the sibling 'get--v3-domain_name-unsubscribes-address'. The description does not mention context, prerequisites, or exclusions, leaving usage unclear beyond the basic purpose.

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