Create Auth Provider

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

Annotations already signal readOnly=false, idempotent=true, etc. The description adds context about Metadata API usage and supported providers but does not disclose potential side effects, conflict behavior, or deployment details. This is adequate but not rich. No contradiction with 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?

Three sentences, front-loaded with purpose, no filler. Each sentence earns its place: what it does, supported types, key inputs/options.

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 tool has 8 parameters and no output schema. The description covers the essential context: purpose, provider types, required credentials, and optional handler. While it doesn't describe return values or additional optional params (defaultScopes, customErrorUrl), the schema covers those, so the description is reasonably complete.

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%, but the description adds meaning by explaining the purpose of consumerKey/consumerSecret ('from the external identity provider') and registrationHandler ('custom user provisioning logic'). It reinforces the providerType enum without being redundant.

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 states a specific verb ('Creates') and resource ('Auth Provider in Salesforce') and clarifies the purpose (SSO or social login via Metadata API). It lists supported provider types, distinguishing it from other creation tools in the sibling set.

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 clearly indicates when to use this tool ('for SSO or social login') and specifies the input requirements ('Provide the consumer key and secret'). However, it does not explicitly mention alternatives or when not to use it, though the context is strong enough.

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