Build Jobber OAuth URL

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

With no annotations provided, the description must convey behavioral traits. It only says 'Build an authorization URL' without mentioning that this is a redirect URL for OAuth, that it requires user interaction, or any side effects. It fails to disclose important aspects like the need for a running web server for the redirect.

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 a single, concise sentence that conveys the core purpose without unnecessary words. However, it could benefit from slight expansion to cover key details without becoming overly verbose.

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 complexity of an OAuth authorization flow and the lack of annotations or output schema, the description is insufficient. It does not explain the broader workflow (e.g., user must visit the URL, then exchange the code), leaving significant gaps for an AI agent to use the tool 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?

The schema has 0% description coverage for its two parameters ('redirectUri' and 'state'). The description does not explain their purposes, constraints, or how they are used in constructing the URL. This leaves the agent without necessary context to provide correct inputs.

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's action ('Build an authorization URL') and the specific context ('for a Jobber admin to connect this customer-hosted MCP server'). It distinguishes itself from sibling tools like jobber_exchange_code and jobber_refresh_token, which handle subsequent OAuth steps.

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 gives no guidance on when to use this tool versus alternatives. For an OAuth flow, it would be helpful to mention that this is the first step before exchanging the code or refreshing tokens. There is no indication of prerequisites or when not to use it.

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