get--v3-domain-tags

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

No annotations are provided, so the description carries full burden. 'List all tags' implies a read-only operation, but it doesn't disclose behavioral traits like pagination (suggested by 'page' and 'limit' parameters), rate limits, authentication needs, or what 'all' entails (e.g., across a domain). This leaves significant gaps for safe invocation.

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 'List all tags'—a single, front-loaded phrase that efficiently states the core action. There's no wasted verbiage, making it easy to parse, though this brevity contributes to gaps in other dimensions.

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, 1 required, no output schema, no annotations), the description is incomplete. It doesn't explain the tool's behavior, parameter usage, or output format, leaving the agent under-informed for a tool with multiple inputs and potential filtering/pagination logic.

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 description adds no parameter semantics beyond the schema, which has 0% description coverage for 5 parameters (domain, page, limit, tag, prefix). Without explanation of what these parameters do (e.g., 'domain' is required, 'tag' might filter), the agent lacks context to use them effectively, failing to compensate for 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 tags' states a clear verb ('List') and resource ('tags'), but it's vague about scope and context. It doesn't specify what kind of tags (e.g., email tags, domain tags) or differentiate from sibling tools like 'get--v3-domain-tag' or 'get--v3-domains-domain-limits-tag', which might handle similar resources differently.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., 'get--v3-domain-tag', 'get--v3-domain-tag-stats'), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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