Discover Holded tools

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

With no annotations provided, the description carries the full burden. It states the tool lists domains, which is inherently read-only, but it does not explicitly disclose that this operation has no side effects or require any authentication. The absence of an explicit read-only statement is a minor gap, though the verb 'List' strongly implies a safe query.

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 two sentences with zero fluff. The primary purpose is front-loaded, and the second sentence adds useful operational detail about sibling tools. 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?

The description does not specify the output format of this tool (e.g., a list of domain names). While the agent can infer the result from the purpose, with no output schema, the description should at least hint at the return structure. The guidance on sibling tools is useful but does not fully compensate for this missing detail.

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 tool has no parameters, and the schema coverage is 100% (empty object), so the description need not add anything. However, it goes beyond the schema by explaining that domain tools take an `action` parameter, which is valuable context for the agent to understand the broader tool ecosystem.

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 tool's function: 'List the Holded tool domains.' It specifies a verb (list) and a resource (tool domains). It also differentiates itself from its siblings by explaining that each domain is a separate tool, making it the entry point for discovering the available domains.

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 clear guidance on how to interact with the sibling tools: call a domain tool with no action to see its actions in the error message, or read the tool description. While it doesn't explicitly say 'use this when you need to discover domains,' the purpose is implied, and the instructions for using alternatives are directly helpful.

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