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

The annotations provide readOnlyHint and idempotentHint, and the description adds valuable context beyond this by explaining that the tool 'Returns the integration recipe' and that 'The agent executes the steps itself — runs terminal commands, edits files, deploys a relay if needed.' This clarifies the tool's non-mutating nature and sets expectations about the agent's follow-up actions. It aligns well with the annotations and adds meaningful behavioral detail.

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 highly concise: two sentences that front-load the primary purpose and immediately follow with the essential behavioral note about the recipe and agent execution. Every sentence earns its place, and there is no redundant or filler content.

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 the tool's simplicity (1 param, 3 enum values), an output schema exists, and the annotations cover safety, the description covers the key contextual points: what the tool does and how the agent must act on the result. A minor gap is the lack of mention of prerequisites (e.g., the form must exist), but this is not critical for invoking 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?

The schema has 100% coverage for the only parameter 'kind', including a detailed description of each enum value. The tool description does not add any additional parameter semantics, so it relies entirely on the schema. This matches the baseline score of 3 for high schema coverage.

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: 'Wire form submissions into a destination.' It identifies a specific verb and resource, making it easy to understand the tool's function. However, it does not explicitly differentiate this from sibling tools like connect_analytics or connect_domain, so it lacks the extra distinction that would earn a 5.

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 tool is used for setting up form-to-destination integrations (telegram, google_sheets, custom), but it provides no explicit guidance on when to use it over alternatives or any exclusions. The purpose is clear enough to infer usage, but there is no direct 'when-to-use' or 'when-not-to-use' statement.

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