subscriber_list

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

No annotations; description does not disclose pagination behavior (limit/offset), default ordering, or any side effects. Agent cannot infer that results are paginated or that domain filter is optional.

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?

Single sentence is concise but lacks depth. Front-loaded with purpose, but omits essential details about parameters and behavior.

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?

Complexity moderate (3 params, output schema). Description fails to cover pagination, defaults, or use cases. Incomplete for a listing tool with multiple parameters and siblings.

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 0%—no parameter descriptions in schema. Description only mentions 'domain' filter, ignoring limit and offset parameters. Leaves 2 out of 3 parameters unexplained.

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?

Clearly states 'List subscribers' with optional domain filter. Distinct from sibling tools like subscriber_get (single) and subscriber_create. Missing explicit differentiation from subscriber_bulk_export.

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 on when to use this tool vs alternatives. Does not mention pagination limits or when to use domain filter. Siblings exist but no differentiation.

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