auth

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

With no annotations, the description provides only a high-level summary without disclosing behavioral details such as session creation/destruction, token expiration, or side effects of accepting terms. This leaves the agent with incomplete expectations.

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, well-structured sentence that front-loads 'Authentication operations'. It is appropriately concise, though it sacrifices detail for brevity.

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 the tool's complexity (6 enum actions, nested data object, no output schema), the description is too sparse to be complete. It does not describe return values, error conditions, or action-specific behavior.

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?

All parameters are documented in the schema with clear descriptions, and the tool description adds no additional semantic value. Per the rubric, baseline is 3 given high schema coverage.

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 identifies this as the authentication tool with specific areas (login flows, token management, terms acceptance), distinguishing it from the project management sibling tools. However, it lacks enumeration of the exact actions available, which are only in the schema.

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 implies usage for authentication operations but does not explicitly specify when to use this tool vs alternatives or when not to use it. It also lacks guidance on choosing between the different actions (e.g., login vs oidcExchange).

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