Forgejo token identity

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond annotations: return fields, 401/403 error conditions, and the fact that it reveals write-attribution identity. No contradiction with annotations.

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 tightly organized: purpose first, then parameters, return shape, usage rationale, and error codes. Every sentence contributes a distinct operational fact with no 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?

There is no output schema, so the description appropriately provides the return fields and error codes, which is enough for a trivial whoami call. The only notable gap is the 'No parameters' statement contradicting the schema's response_format parameter, but since the schema documents that parameter fully, the operational impact is limited.

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 schema fully documents response_format with enum and default, so the description did not need to repeat it. However, the description's claim 'No parameters' conflicts with the schema's single optional parameter, giving an agent contradictory guidance about whether a parameter can be supplied. This is a genuine correctness issue rather than merely a coverage gap.

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: it returns the Forgejo account associated with the token used for the call. This clearly identifies the tool as a token-identity/validation operation and distinguishes it from the sibling repo/issue/PR tools.

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 explicitly tells the agent when to use it: to confirm a token is valid and to know which identity writes will be attributed to, before creating an issue or pull request. It does not list when-not-to-use alternatives, but no close alternative exists among the siblings, so the guidance is clear enough.

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