use_magic_link

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

The description fully discloses that the tool snapshots localStorage and a header to a file, and clarifies that the magic_link_url is not navigated to. Annotations only say readOnlyHint=false, so the description adds substantial behavioral context.

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 concise and front-loaded with the primary action. It efficiently covers prerequisites, mechanism, and usage context in four sentences without redundancy.

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?

The description covers prerequisites, behavior, and integration with other tools. Minor gaps include lack of explicit mention of file overwrite behavior or error handling, but overall it is sufficiently complete for a single-parameter tool.

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 input schema already provides a detailed description for magic_link_url. The tool description adds context by explaining its role in deriving the portal origin and its non-navigational nature, enhancing understanding beyond 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?

The description clearly states the tool captures a HoneyBook client-portal session using a browser extension. It distinguishes itself from sibling tools (workspace, payment, contract operations) by focusing on session capture.

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 explains prerequisites and notes that all other tools use the most-recently-activated session, implying this tool is used to establish a session before others. However, it doesn't explicitly describe when not to use it or name direct alternatives.

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