manage_forms

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

With no annotations provided, the description carries full burden. It discloses that adding a subscriber triggers double opt-in if enabled, which is valuable behavioral context. However, it doesn't cover other important aspects like authentication requirements, rate limits, error conditions, or what happens when listing forms with no data.

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 extremely concise and well-structured. It uses a single sentence to explain the tool's purpose and actions, with no wasted words. Every element earns its place, and the information is front-loaded with the core functionality.

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 no annotations, no output schema, and zero parameters, the description provides adequate but minimal context. It explains what the tool does and mentions the double opt-in behavior, but doesn't cover return formats, error handling, or integration with sibling tools. For a tool with three distinct actions, more detail about outputs would be helpful.

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 has 0 parameters with 100% coverage, so there are no parameters to document. The description appropriately doesn't waste space discussing nonexistent parameters. A baseline of 4 is appropriate for zero-parameter tools where the schema already indicates no inputs are required.

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 purpose: managing Kit forms with three specific actions (list forms, list subscribers, add subscriber). It uses specific verbs and resources, but doesn't explicitly differentiate from sibling tools like manage_subscribers or manage_segments that might overlap in subscriber management.

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 about when to use this tool versus alternatives. The description lists actions but doesn't explain when to choose list_subscribers here versus manage_subscribers, or when form-based subscriber management is appropriate versus other subscriber management approaches.

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