dynadot_folder_list

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

With no annotations, the description carries full burden but only states 'List domain folders.' It does not disclose whether the operation is read-only, requires authentication, or has rate limits. The schema suggests pagination, but the description omits behavioral details.

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?

While the description is very short (four words), it is under-specified rather than concise. Important information about parameters and behavior is missing, making it inadequate for agent comprehension.

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 tool has two undocumented parameters, no output schema, and no annotations, the description is severely incomplete. An agent cannot determine how to paginate results or understand the response format.

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 defines two parameters (pageIndex, countPerPage) with 0% description coverage. The description does not explain their purpose, format, or range, leaving the agent without essential guidance for correct invocation.

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 'List domain folders' clearly states the action (list) and resource (domain folders), distinguishing it from sibling tools like create_folder, delete_folder, or set_folder_*. However, it does not specify the scope (e.g., all folders or user-specific), which could be clarified.

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 is provided on when to use this tool versus alternatives like dynadot_folder_info or dynadot_create_folder. There is no mention of prerequisites or context for choosing this tool.

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