authenticate

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

With no annotations, the description carries the full burden. It discloses key behavior: it caches the session and the force parameter allows a fresh login. However, it omits how authentication is performed, what happens on failure, or where the session is stored, which are important for an auth tool.

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 compact: one clear purpose sentence and one parameter explanation. No wasted words, and the key information is front-loaded.

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 one-parameter auth tool with no output schema and no annotations, the description covers the core behavior and parameter semantics. It could mention that authentication is a prerequisite for sibling tools, but the session-caching clue makes that reasonably inferable.

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 0%, and the description fully compensates for the single parameter. It explains that force=true ignores the cached session and logs in fresh, which implies the default reuses the cache. This is complete and goes beyond the bare schema type and default.

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 a specific verb and resource: 'Authenticate to Forgejo and cache the session.' This clearly distinguishes the tool from all siblings, which are project, milestone, and issue operations rather than authentication.

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 this is the gateway to Forgejo operations by mentioning session caching, and there are no alternative auth tools among siblings. However, it does not explicitly state that this should be called before other tools or that a cached session is automatically reused unless force is set.

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