List newsletter subscribers

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose one meaningful behavior: subscribers are returned most recent first. However, it does not mention the default limit behavior, pagination, or what subscriber fields are included, so transparency is only partial.

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 a single, front-loaded sentence with no filler. Every word adds value: the resource is identified, and the ordering behavior is specified.

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 one-parameter list tool, the description plus schema is largely sufficient. The resource, ordering, and optional limit are understandable. A minor gap is that the description does not clarify that the default limit of 100 means the tool may return only a subset of subscribers.

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 does not mention the 'limit' parameter at all, and schema description coverage is 0%. The schema provides constraints and a default, but the description adds no semantic context to help an agent understand how the limit affects the returned list.

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 ('List') and the resource ('email newsletter subscribers'), and adds ordering ('most recent first'). It is unambiguous about what the tool does, though it does not explicitly contrast it with sibling tools like list_newsletter_sends.

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 gives no guidance on when to choose this tool over alternatives such as list_newsletter_sends or list_consultation_requests. It implies the use case through the resource name, but never states conditions, exclusions, or related tools.

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