Connect to Editor

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

With no annotations, the description carries the burden for behavioral context. It discloses that users see an avatar while connected, that compose tools disconnect when done, and that returns a token and room ID. However, it does not state whether the connection persists until disconnect-from-editor is called, any limits on concurrent connections, or what happens if the agent connects while another is already connected.

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 compact and well-structured with bold section labels (Purpose, When to use, Returns). Every sentence adds value, and the key information is front-loaded in the first line.

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, the description covers purpose, usage, exclusions, and return values. Minor gap: it does not explicitly mention the need to call disconnect-from-editor when the agent is done outside compose workflows, but the sibling tool name implies this. Overall complete enough for correct invocation.

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% for all 3 parameters, so the schema already provides full parameter documentation. The description does not add meaningful semantics beyond returning a token/room ID, so baseline 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 states a specific purpose ('Show agent presence in the Resend dashboard editor') with a clear verb-resource pairing. It distinguishes this tool from siblings by explaining when it is not needed (before compose-broadcast/compose-template) and that get-tiptap-json-content connects automatically.

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 explicit when-to-use guidance: signal agent presence outside compose workflows. Also explicitly lists exclusions ('Not needed before compose-broadcast or compose-template') and names an alternative (get-tiptap-json-content), which is exactly the kind of guidance needed.

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