Create Connected App (OAuth)

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

Annotations already disclose that the tool is non-read-only and idempotent. The description adds no further behavioral traits such as requiring admin permissions, deployment via Metadata API, or generation of consumer keys and secrets. It does not contradict any annotations.

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 concise sentences, front-loaded with the core purpose, and contains no unnecessary content. It is well-structured and easy to scan.

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 description clearly explains the tool's purpose and typical use cases, but since there is no output schema, it does not explain what the tool returns. Important operational caveats (e.g., Client Credentials Flow needing Setup UI) exist only in parameter descriptions, leaving some ambiguity for the 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?

The schema has 100% description coverage for all 11 parameters, so the description's mention of callback URLs and OAuth scopes adds little beyond the schema. It reinforces key parameters but does not provide deeper semantic meaning.

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 it creates a Connected App for OAuth authentication, using a specific verb and resource. It distinguishes this tool from siblings by explaining its role in enabling external system integrations via OAuth 2.0.

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 clear when-to-use context, stating that Connected Apps are required for any external system using OAuth 2.0 and listing common use cases (web, mobile, desktop, server-to-server). However, it does not explicitly mention when not to use it or point out the alternative sf_create_external_client_app.

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