list_topics

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the HTTP method (GET) and the domain-first scoping, which signals a read-only operation, but it does not describe pagination behavior, ordering, or what fields are returned.

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 sentence that front-loads the action and resource, then adds the endpoint reference. There is no fluff or repetition; every part earns its place.

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 list tool, the description plus schema is mostly adequate: the domain parameter is required and clear, and the tool's purpose is obvious. However, the lack of output schema and the unexplained optional pagination parameters leave some gaps for an agent that needs to call this correctly in non-trivial scenarios.

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 description coverage is only 25%: domain is documented, but after, limit, and before have no descriptions. The description itself only mentions the domain parameter and does not compensate for the undocumented pagination-related parameters, leaving their meaning and formatting ambiguous.

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 names a specific verb ('List'), a resource ('sending domain's subscription topics'), and includes the exact endpoint, making it unmistakable what the tool does. It is also distinct from siblings like get_topic (single topic) and create_topic/update_topic/delete_topic (mutations).

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 makes clear the tool is for listing topics scoped to a sending domain, which implies it should be used when you need multiple topics for a domain. However, it does not explicitly contrast it with get_topic, create_topic, or other topic-related tools, leaving the when/when-not guidance implicit rather than explicit.

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