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

While annotations already declare readOnlyHint, idempotentHint, and destructiveHint, the description adds valuable behavioral context: it returns instructions (not performing the migration), warns to call every guidance and not to update components/hooks until specific guidance is received, and implies a sequential workflow. This enriches the annotations without contradiction.

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 sentences, front-loaded with the primary purpose, and every sentence adds distinct value: purpose, alternative tool usage, list of guidance topics, and critical warnings about order and updating. No fluff or redundancy.

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 the presence of an output schema (so return values need not be explained), annotations covering safety, and only three optional parameters with enums, the description is highly complete. It covers when to use, how to use, and important caveats, making it sufficient for an agent to invoke the tool correctly.

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?

Despite 0% schema description coverage, the description compensates by explaining the 'guidance' parameter's purpose ('Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more') and the need to call it repeatedly. It also relates 'fullstack_framework' to Next.js App Router/Pages Router. However, 'migrating_from' is only implied via 'existing auth provider', not explicitly tied to the parameter.

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 tool's purpose: 'Returns instructions for migrating from an existing auth provider to PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application.' It identifies a specific verb, resource, and scope, and distinguishes itself from the sibling tool by explicitly referencing migrate_to_propelauth_frontend for frontend-only use cases.

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 explicit usage guidance: says to use migrate_to_propelauth_frontend when Next.js is used as just a frontend, and instructs to use the 'Installation' guidance first and call every guidance for a successful integration. This goes beyond basic context by giving a clear alternative and step-by-step process.

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