pirsch_list_domains

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

With no annotations provided, the description carries full burden. It correctly indicates a read-only listing operation but does not disclose any potential side effects, rate limits, authentication requirements, or result format. The description is minimal but truthful.

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, focused sentence that conveys the entire purpose with no redundant words. Every word 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?

Given the lack of output schema, the description does not explain what data is returned (e.g., fields, pagination). The 'search' parameter is undocumented, leaving the agent guessing its behavior. For a tool with one parameter and no output schema, more context is needed.

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 one parameter ('search') with zero description coverage. The tool description does not mention this parameter or explain its meaning (e.g., filtering by domain name). The description adds no value beyond the schema structure.

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 action ('List'), the resource ('accessible Pirsch domains'), and the purpose ('to discover domain IDs'). It distinguishes this tool from its siblings (e.g., pirsch_visitors, pirsch_pages) by focusing solely on domain discovery, not analytics data.

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 implies that this tool is used to obtain domain IDs for subsequent API calls, but it does not explicitly state when to use it versus alternatives or when not to use it. No guidance on prerequisites or usage context is provided.

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