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

Beyond the annotations' safety hints, the description adds important behavioral context: the authorization link is one-time, the token lasts 60 days, no refresh token is issued, and reconnection requires this same tool. These details are essential for correctly using and revisiting the connection.

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 two tightly written sentences. The core action is front-loaded, and the token-lifetime caveat is placed immediately after without any 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?

Given the tool has no parameters and an output schema is provided, the description covers what the agent needs: what the tool does, what it returns conceptually (an authorization link), and the token lifecycle limitation. Nothing essential 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 has zero parameters, so the schema has nothing to document and the description appropriately does not discuss parameter semantics. The baseline for a no-parameter tool is 4.

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 uses a specific verb ('Generates') and resource ('one-time authorization link to connect a Meta (Facebook/Instagram) ad account'), making the tool's purpose immediately clear and distinguishable from other platform-connection siblings.

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 clearly implies the primary usage context — connecting a Meta ad account — and explicitly tells the agent to reuse the same tool when the token expires. It does not name alternatives or when-not conditions, but the reconnection guidance is concrete.

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