config__open_relay

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

Annotations provide basic but indirect hints; the description adds key behavioral details: auto-respawns the daemon if dead, opens a browser, and returns specific state. This goes beyond annotations.

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 concise sentences front-load the primary action and returns. No unnecessary words; everything is relevant.

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 no-param tool with no output schema, the description fully covers the purpose, side effects (browser launch, auto-respawn), and return values (URL, launch status, credential state).

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?

No parameters in schema, so baseline 4 applies. Description adds no parameter info (unneeded) but confirms the tool has no inputs.

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 action (opens relay configuration form) and the resource (better-notion-mcp in user browser), with a specific verb and result. It distinguishes from sibling 'config' by specifying relay configuration.

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 does not provide explicit guidance on when to use this tool versus alternatives, though it implies usage for opening relay config. It mentions auto-respawn but lacks exclusions or context for when not to use.

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