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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds useful context by clarifying that the tool does not actually modify state; instead, it returns a recipe that the agent executes itself (terminal commands, file edits, relay deployment). This goes beyond the annotations and helps the agent understand the actual workflow without contradiction.

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 two sentences: the first states the purpose, the second explains the behavioral model. It is concise, front-loaded, and contains no fluff. Every sentence carries meaning.

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 simple 1-parameter tool with full schema coverage, annotations, and an output schema, the description adequately covers the purpose and the execution model. The agent has all necessary information to decide when to call it and 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?

The only parameter 'kind' has a complete schema description (100% coverage) explaining each enum value. The description itself does not add any additional parameter-level meaning, so it relies on the schema. Baseline of 3 is appropriate.

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 action: 'Wire form submissions into a destination.' It also specifies the output type ('Returns the integration recipe'), which aligns with the name and title. The schema's 'kind' enum further distinguishes this from sibling tools like connect_analytics or connect_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?

The description implies the usage context (when you need to direct form submissions to a destination) and is clear about the tool's role. However, it does not explicitly mention alternative tools or when NOT to use it, which would merit a 5. Still, the context is clear enough for the agent to decide.

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