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

The description discloses that it only returns instructions and includes a specific behavioral rule: 'Do not update the guidance argument unless the user explicitly requests it.' This adds context beyond the annotations and aligns with the readOnlyHint and idempotentHint flags. 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?

The description is front-loaded with the main function and is concise overall. The sentence 'It is important to follow the instructions carefully' is generic filler but not distracting.

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 that an output schema exists and the tool is a read-only instruction provider, the description is sufficiently complete. It covers the main query dimensions (backend framework and guidance topics), though it omits explicit mention of parameter defaults and alternative tool choices.

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 description coverage is 0%, but the description compensates by mapping guidance topics (installation, protecting API routes, org membership) to the guidance enum and listing backend frameworks that align with the backend_framework enum. It adds meaning to both parameters, though it does not explain defaults or null behavior.

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 'Returns instructions for integrating PropelAuth in a backend framework' and lists specific frameworks and guidance topics. This makes the tool's purpose specific and distinguishes it from sibling tools like integrate_propelauth_frontend or fullstack by emphasizing backend scope.

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 gives clear context that this tool is for backend framework integration, which implies when to use it. However, it does not explicitly mention alternatives or when not to use it, so it lacks exclusions.

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