dynadot_contact_list

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

The description mentions pagination but does not elaborate on behavior such as default page size, ordering, or whether the operation is read-only. With no annotations, the description carries the full burden but provides minimal behavioral information.

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 is perfectly concise and front-loaded with the action. No extraneous words are present.

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 two parameters, no output schema, and several sibling list tools, the description is too brief. It fails to explain pagination details, parameter constraints, or what the response looks like, leaving the agent with insufficient information to invoke the tool correctly.

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 coverage is 0% (no parameter descriptions). The word 'paginated' hints at the purpose of pageIndex and countPerPage, but does not explain their meaning, defaults, or valid ranges. The description adds little beyond the schema.

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 'List all contacts in the account (paginated).' It specifies the action (list) and the resource (contacts), and distinguishes from sibling list tools like 'dynadot_domain_list' by focusing on contacts.

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 such as 'dynadot_get_contact' (single contact) or other list tools. The description lacks context on appropriate usage scenarios.

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