Exchange Jobber OAuth Code

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

With no annotations, the description must fully disclose behavioral traits. It mentions 'store tokens locally' but does not specify where or how tokens are stored, whether prior tokens are overwritten, or any authentication or rate-limit requirements. This leaves important side effects ambiguous.

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 sentence of 13 words, which is concise but lacks scannability. It is not front-loaded with critical details; the key verb 'exchange' is present, but the mention of storing tokens is vague.

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 no output schema, no annotations, and 0% parameter coverage, the description is severely lacking. It does not explain the result of the exchange, how the stored tokens are used, error states, or the relationship to sibling tools in the OAuth flow.

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?

Input schema has 0% description coverage, and the description adds no meaning to the two parameters (code and redirectUri). The code parameter requires minLength 8, and redirectUri has a URI format, but the description gives no context about their purpose or format.

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 action ('exchange') and resource ('Jobber OAuth authorization code') and mentions storing tokens. However, it doesn't differentiate from sibling tools like jobber_auth_url or jobber_refresh_token, which could confuse an agent about which step of the OAuth flow this tool corresponds to.

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 no guidance on when to use this tool versus alternatives. Sibling tools include jobber_auth_url (to obtain the code) and jobber_refresh_token (to refresh credentials), but the description does not clarify prerequisites or the expected sequence of calls.

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