Reauthenticate

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

The description says 'trigger re-authentication,' which implies a state-changing operation, but the annotations declare readOnlyHint: true. This contradiction is not reconciled, and no additional behavioral details are provided.

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, clear sentence with no fluff, making it highly concise and front-loaded. Every word earns its place.

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 description lacks usage context and behavioral details, and the contradiction with readOnlyHint creates confusion. It is minimally complete for a zero-parameter tool, but the contradiction and lack of guidance reduce completeness.

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 tool accepts no parameters, so the description need not explain them. Baseline score of 4 applies for zero-parameter tools.

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 action (trigger re-authentication) and the target resource (Client Portal Gateway session), which distinguishes it from sibling tools like get_auth_status or ping_session.

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 mention of when to use this tool, when not to use it, or alternatives. It fails to provide context for when re-authentication is needed or how it relates to other session-oriented tools.

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