use_flow_link

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

With only readOnlyHint=false in annotations, the description carries the full behavioral burden and does it well: it discloses the localStorage snapshot, the exact destination file, the weak-auth scope limitations, and the per-questionnaire re-approval behavior. No contradiction with 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?

The description is dense but every sentence earns its place: purpose, usage distinction, prerequisites, mechanism, security scope, and caveat. It is front-loaded with the core purpose and avoids filler.

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 credential-capture tool with one parameter, no output schema, and meaningful security nuance, the description covers prerequisites, behavior, output location, limitations, and alternatives. An agent has enough context to select and invoke it correctly.

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 the baseline is 3, but the description adds meaningful value by explaining that only the /flow/<flowId> segment is required and that ?hash= is only a fallback. This helps an agent choose and format the URL correctly.

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 opens with a specific verb ('Capture') and resource ('HoneyBook QUESTIONNAIRE credential'), then clearly scopes the tool to /flow/<flowId> links. It explicitly differentiates from use_magic_link by naming the client-portal link shape that should use the sibling instead.

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?

It gives explicit when-to-use guidance for flow links, and an explicit when-not-to-use with a named alternative. It also lists concrete prerequisites: install the extension, open the link, let the page render, then run the tool.

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