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

With no annotations provided, the description carries the full burden. It discloses the sensitive nature of the response (new client_secret), instructs to update authorized OAuth clients immediately, and warns not to log the secret. These are behavioral traits beyond what structured fields provide.

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 four short sentences plus a cost note. Every sentence earns its place: purpose, sensitivity warning, usage prerequisite, return value, and cost. It is front-loaded with the primary action and contains no fluff.

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 is complete for the tool's complexity. It covers the sensitivity, prerequisite call, parameter targeting, and return value. The presence of an output schema handles return details, and the description adds the critical 'do not log the secret' guidance. No significant gaps remain.

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 input schema has 100% coverage with descriptions for both parameters. The description adds value by explaining how to obtain clerk_instance_id (via get_connected_accounts), the default behavior when omitted, and clarifies the role of oauth_application_id in the rotation context.

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: 'Rotate the client secret for a confidential OAuth application in a connected Clerk application.' The verb 'rotate' is specific and distinguishes this from sibling tools like create_oauth_application, delete_oauth_application, and get_oauth_application.

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?

Provides clear usage guidance: 'Call clerk.get_connected_accounts first' and explains how to target a connection via clerk_instance_id or default. It does not explicitly mention alternatives or when-not-to-use, but the context is solid enough for an agent to choose this tool appropriately.

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