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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds value with the caveat 'Do not update the guidance argument unless the user explicitly requests it,' which clarifies a subtle behavioral constraint beyond standard read-only semantics.

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 focused sentences, each earning its place: purpose, alternative, and parameter caveat. It is front-loaded and free of redundancy or 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 tool has an output schema, so return values need no explanation. The description covers purpose, scope, alternative, and parameter behavior. It could be slightly more explicit about when to use the backend variant, but for a well-scoped integration-guidance tool it is sufficiently 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 0%, but both parameters have self-descriptive names and enums in the schema. The description partially compensates by listing example guidance topics ('installation and configuration, retrieving user or org information, logging users out') and by mentioning App Router/Pages Router, which maps to the fullstack_framework enum. However, it adds limited meaning beyond the schema's enums and defaults.

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 opens with a specific verb+resource+scope: 'Returns instructions for integrating PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application.' It clearly distinguishes from the frontend sibling by naming integrate_propelauth_frontend, making the tool's purpose unmistakable.

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 an explicit when-not and alternative: 'If the user is using Next.js as just a frontend ... use the integrate_propelauth_frontend tool.' It also implies the intended context (fullstack Next.js) and lists typical use cases, giving an agent clear decision criteria.

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