forgejo_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does this well by revealing that the tool reads credentials from specific environment variables, may authenticate on demand, and persists the session under the OS config directory. This goes beyond the surface-level 'status' meaning of the name.

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?

Two short sentences, front-loaded with the core purpose, followed by the side effects and credential details. No redundant wording or filler.

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 zero-parameter status tool with no output schema, the description conveys the essential purpose, credential sources, and side-effect behavior. It could be slightly more explicit about the exact return format (e.g., a boolean), but 'Report whether' is reasonably sufficient for an agent to use 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?

The tool has zero parameters, so there is no parameter semantics to add. The description instead usefully explains the credential sources (FORGEJO_URL / FORGEJO_USERNAME / FORGEJO_PASSWORD), which is the closest analog to parameter documentation here.

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 uses a specific verb ('Report whether') and a precise resource ('the MCP is authenticated to the Forgejo instance'). This clearly distinguishes it from the sibling 'authenticate' tool, which handles authentication itself.

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 right tool for checking authentication status before other operations, and it notes that authentication happens automatically if needed. However, it does not explicitly contrast it with the sibling 'authenticate' tool or state when one should be preferred over the other.

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