Connect your Jobber account

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

With no annotations, the description carries the full burden and does so: it discloses the OAuth browser flow, local token storage, that it is a one-time operation, the exact scopes required, and the fallback behavior when credentials are absent. This is unusually rich behavioral disclosure for an auth tool.

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-loads the purpose, then the prerequisite, then the invocation contract, then the no-credentials fallback. Length is justified by the multi-step setup the agent must relay; no sentence is 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?

Covers the full setup and invocation path including the degraded no-credential case, and with no output schema or annotations it is nearly complete. It stops short of describing token lifetime, refresh, or what happens if stored tokens expire, which an agent may need for follow-up calls.

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 client_id and client_secret are already documented, giving a baseline of 3. The description adds real meaning by tying the values to the user's Jobber developer app and explaining that calling without them is valid (consistent with required=0), which the schema alone does not convey.

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?

States a specific verb (connect/authenticate) and resource (the user's Jobber account) via OAuth, and explicitly frames it as a one-time setup action. This clearly separates it from every sibling, all of which are read/query tools for jobs, invoices, quotes, etc.

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?

Gives an explicit prerequisite (create a developer app with read-only scopes, leave Callback URL blank) and an explicit no-credential path: calling without credentials returns setup instructions to relay to the user. The agent knows both when and how to invoke it.

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