jwt_add_blacklist

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states that it 'Generate token blacklist and revocation' with no mention of side effects, whether existing tokens are invalidated, authorization requirements, or what happens to current sessions.

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 a single compact sentence that states the core function and the Pro limitation up front. It is not padded, though the brevity comes at the cost of needed operational detail.

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 no annotations, no output schema, and an underspecified api_key parameter, yet the description does not explain expected inputs, effects, or return values. An agent cannot fully determine how to invoke this tool correctly beyond knowing a directory is required.

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 schema provides descriptions for only one of two parameters (directory), and the description adds no parameter-level meaning. In particular, the required 'api_key' parameter is undocumented in both the schema and the description, leaving its purpose and format ambiguous.

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 names a specific action ('Generate') and a resource ('token blacklist and revocation'), and the 'Pro feature' marker adds a capability signal. It is reasonably distinguishable from siblings like jwt_add_refresh, though 'blacklist' is ambiguous as to whether it generates a list or configures blacklisting/revocation behavior.

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?

No guidance is provided about when to use this tool versus alternatives such as jwt_add_refresh or jwt_generate_auth. The description does not mention prerequisites, integration context, or excluded cases.

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