get_login_link

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

Discloses that it returns a clickable link and uses cached token if no access_token provided. Without annotations, it provides good behavioral context, though could mention prerequisites like prior authentication setup.

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?

Concise, well-structured with a note on usage, parameter description, and return value. Front-loaded with purpose.

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 simple tool (one optional param, output schema present), the description covers purpose, usage guidelines, parameter semantics, and return type completely.

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?

With 0% schema coverage, the description adds full meaning: 'access_token: Meta API access token (optional - will use cached token if not provided)' clarifies parameter role and behavior.

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 it 'Get a clickable login link for Meta Ads authentication,' using a specific verb and resource. Among sibling tools focused on ad operations, this authentication tool is distinctly different.

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?

Explicitly tells when to use (own Facebook app) and when not (recommended Pipeboard authentication with environment variable). Also advises on parameter usage.

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