authenticate

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

The description adds valuable context beyond annotations: it explains that this tool establishes a session for authentication, which is crucial for understanding its behavioral impact. Annotations only indicate it's not read-only, but the description clarifies its purpose in enabling other tools. No contradiction with annotations exists.

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 and concise, with two sentences that efficiently convey purpose and usage guidelines. Every sentence earns its place without unnecessary details, making it easy for an agent to parse.

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 (authentication setup), no output schema, and minimal annotations, the description is mostly complete. It explains what the tool does and when to use it, but could benefit from mentioning potential errors or session details. However, it adequately covers the essentials for an agent to invoke it correctly.

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?

With 0 parameters and 100% schema coverage, the description doesn't need to explain parameters. It appropriately focuses on the tool's purpose and usage, adding no redundant information. A baseline of 4 is justified as it compensates for the lack of parameters by emphasizing context.

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 specific action ('Create a TGC session') and resource ('using stored credentials'), distinguishing it from sibling tools like 'logout' or other authentication-related operations. It precisely communicates the tool's function without being tautological.

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?

It explicitly states when to use this tool ('Must be called before any tool that requires authentication'), providing clear context and prerequisites. This helps the agent understand its role as an initialization step in the workflow.

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