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

Annotations declare a non-read-only, non-destructive, non-idempotent operation, and the description adds genuinely useful context beyond them: the link expires in 15 minutes, it lifts the free 10-design cap to 25/day and 150/month, and it saves designs to the account. These are concrete behavioral traits the annotations cannot convey.

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?

Front-loaded with what the link is and does, then the expiry, then the call-to-action. Slightly verbose in cataloguing the design allowances, but every clause adds decision-relevant information.

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 zero-parameter tool with a full-coverage schema and no output schema, the description covers what the link does, its lifetime, and the expected interaction flow. Nothing critical for correct invocation is missing.

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 tool takes zero parameters, so there is no parameter semantics for the description to supply. Baseline 4 applies.

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 produces a link that connects the chat to the user's PatchDesign.AI account, a specific verb+resource. It does not, however, differentiate itself from siblings like order_link or quote_patch, which are also link-generating tools.

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 procedural guidance ('Give it to the user, then continue once they say they have connected') but never states when to reach for this tool versus the sibling link tools, nor any precondition for when a user actually needs to sign in.

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