begin_account_auth

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

No annotations are provided, so the description must carry the burden. It only states that it starts onboarding and accepts credentials formats, but gives no details on side effects, return values, interactive steps, or failure modes. This is a significant gap 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?

The description is a single concise sentence that is front-loaded with the action and includes the key input detail. No wasted words.

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?

With five parameters, no annotations, and no output schema, the description should explain the OAuth lifecycle, any prerequisites, and how this relates to finish_account_auth. It only gives a minimal overview, which is inadequate for an unfamiliar agent.

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% with descriptions for all five parameters. The description adds that credentials can be provided as JSON or path, but this largely duplicates the schema fields. It doesn't clarify precedence or whether any parameter is conditionally required.

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 'Start OAuth onboarding for an account' with a specific verb and resource. Accepting credentials JSON or a path adds detail. The name contrasts with the sibling finish_account_auth, making the purpose unambiguous.

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 implies this is the entry point for OAuth authentication by saying 'Start OAuth onboarding,' but it doesn't provide explicit when-to-use instructions or mention alternatives like finish_account_auth. The context is somewhat clear but no exclusions are given.

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