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

Annotations declare destructiveHint=true and idempotentHint=false; the description adds genuinely new behavior the annotations cannot express: the code is single-use, expires in 15 minutes, and the returned keys are shown only once. It does not spell out that the consumed code becomes invalid or what permissions the new keys grant, but it goes well beyond the annotation surface.

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?

Two dense sentences, front-loaded with the action and input source, then the return contract. No filler and nothing repeated from the title.

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 no output schema, the description correctly carries the return contract (server key and browser key, shown once, plus host configuration examples) while also covering input provenance and expiry. An agent has everything needed to call it and handle the result.

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 description coverage is 100%, with the code format (7K2M-QX4T, dashes optional) and the client enum already documented in the schema, so the baseline is 3. The description adds only that the code is single-use with a 15-minute validity window, which is marginal extra meaning over the schema.

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?

States a specific verb (Connects) and resource (a Tyton site to this connection) plus the mechanism (single-use pairing code). It is clear what the tool does, though it never names which sibling to use instead (e.g. setup_server, check_live_setup), so an agent must infer its place in the setup flow.

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?

Gives a concrete prerequisite and source for the input: the code comes from the site's card on usetyton.com and is valid for 15 minutes. Usage context is therefore clear, but there is no explicit when-not guidance or comparison to the many sibling setup/connection tools.

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