jwt_add_refresh

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

No annotations are present, so the description carries the full burden. It only says 'Add refresh token rotation flow' without explaining side effects, files modified, whether existing JWT setup is required, or whether the operation is idempotent. The 'Add' verb implies non-destructive behavior but little else.

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 very concise and free of filler, but it is so terse that it borders on under-specification. It has no structural issues, yet it does not provide enough substance to be considered well-rounded.

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?

For a tool with no annotations and no output schema, the description is incomplete. It does not clarify what 'refresh token rotation flow' entails, where it is applied, whether existing auth code is expected, or what the api_key is for. The directory parameter is the only semi-clear context signal.

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 only 50%, with api_key undocumented and directory only briefly described. The description does not explain how either parameter is used or why they matter to the refresh token rotation flow, so it fails to compensate for the schema gap.

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 the verb 'Add' and the resource 'refresh token rotation flow', making the tool's purpose reasonably clear. It differentiates from siblings like jwt_add_blacklist and jwt_generate_auth at a high level, though 'flow' remains somewhat vague.

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?

There is no guidance on when to use this tool versus alternatives such as jwt_generate_auth or jwt_add_blacklist. No prerequisites, integration steps, or context for choosing this tool are provided.

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