pfm_create_social_account_auth_url

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

No annotations are present, so the description carries the full burden. It discloses a notable behavioral limitation (redirect_url_override is not accepted for Quickstart) and explains how permissions affect future behavior. However, it doesn't mention whether generating a URL creates a pending connection or has any side effects, leaving some safety ambiguity.

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 three sentences long, front-loaded with the primary action, and every sentence provides actionable information. No fluff or repetition of schema details. The structure is ideal for quick parsing by an AI agent.

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 tool has 5 parameters, nested objects, and no output schema, yet the description covers the essential flow and key caveats. While it doesn't mention platform_data requirements (like Bluesky's handle/app_password), the schema already documents these sufficiently. The description is complete enough for the tool's core function, though a bit more about the response format would have helped.

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. The description adds value beyond the schema by clarifying that redirect_url_override is not available with system credentials and by advising to include 'feeds' for later feed access. These details help interpret the parameters correctly, pushing the score above baseline.

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 and resource: 'Generate an OAuth URL to connect a user's social media account.' This clearly distinguishes the tool from siblings like pfm_create_social_account, which likely creates an account record directly. It also explicitly describes the OAuth redirect flow, making the tool's function unmistakable.

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 provides immediate instructions: 'Redirect the user to this URL; they'll be redirected back after auth.' It also gives a usage constraint (Quickstart/system credentials) and a recommendation (include 'feeds'). However, it doesn't explicitly contrast with pfm_create_social_account or state when not to use this tool, so it stops short of full alternative guidance.

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