connect

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

Adds important auth context (active account requirement) not present in annotations. Explains the open-world behavior (public URL creation) which aligns with openWorldHint=true. Annotations already disclose non-read-only and non-idempotent traits, so description appropriately adds operational context rather than repeating safety flags.

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?

Three tightly structured components: purpose declaration, auth prerequisite, and concrete example. Every clause earns its place with zero redundancy. Information density is high and front-loaded.

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 annotations covering safety/idempotency and schema covering parameters, the description successfully establishes complete operational context: tunnel creation mechanism, URL forwarding behavior, and authentication requirements. No output schema exists but the result structure is evident from the example.

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 coverage is 100% so baseline is 3. The example ('connect port 3000 with subdomain my-app to get https://my-app.yourdomain.com') significantly clarifies the semantic relationship between 'subdomain' parameter and resulting URL structure, adding concrete value beyond schema definitions.

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?

Clear specific description of what the tool does (starts tunnel, forwards public URL to local port). Includes concrete example showing the forwarding mechanism. Does not explicitly differentiate from sibling 'create_tunnel' though 'Start' vs 'Create' implies a distinction.

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 critical prerequisite ('Uses the active account from pie login') and concrete example showing parameter usage and expected URL outcome. While it lacks explicit 'when not to use' guidance, the prerequisite and example provide clear usage context.

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