dynadot_set_folder_stealth

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

With no annotations, the description must bear full burden. It does not explain side effects (e.g., overwrites existing stealth settings), idempotency, or authentication requirements. The term 'apply' is vague.

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?

Single sentence with no waste, but overly terse given the tool's complexity and missing context. Balanced conciseness with completeness would require more detail.

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 tool with 3 parameters and many siblings, the description lacks enough detail to enable correct selection and invocation. No output schema means agents do not know what to expect.

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 has 0% description coverage. Description does not explain folderId (how to obtain), stealthUrl (valid format), or stealthTitle (purpose beyond 'title'). Agents cannot infer parameter meaning.

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?

Description clearly states verb 'apply' and resource 'stealth forwarding' with scope 'to all domains in a folder', distinguishing it from sibling tool set_stealth_forwarding which likely applies to a single domain.

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 on when to use this tool versus alternatives like set_stealth_forwarding or set_default_stealth. No prerequisites mentioned (e.g., folder must exist).

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