customize_signup_form

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

Discloses that the tool is mutating (customize), respects read-only/dry-run modes, requires API key, and has concurrency limits. No contradictions with annotations (readOnlyHint=false).

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?

Well-organized: one-sentence purpose, followed by a usage note, then parameter details. Every sentence adds value without redundancy.

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?

With output schema present (though not shown), the description adequately covers purpose, prerequisites, parameter details, authentication, and return value. No missing context for this customization tool.

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?

Despite 0% schema coverage, the description fully explains all parameters with examples and references to other tools (list_audiences, list_accounts). Clear structure for header, contents, styles, list_id, and account.

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 explicitly states the verb 'customize' and the resource 'audience's default signup form' with specific items (header, content sections, styles). It distinguishes from sibling tools like list_signup_forms.

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?

Provides explicit guidance: at least one of header/contents/styles must be provided, and recommends using list_signup_forms first to inspect the current form. Also mentions authentication, concurrency limits, and dry-run mode.

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