github_whoami

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

No annotations exist, so the description carries the full behavioral burden. It conveys that the call is non-mutating and touches the configured token, but says nothing about failure behavior (e.g., what happens with an invalid or expired token), whether it performs a live API call, or whether scopes/permissions are reported. Adequate for a trivial read, but the error path is undisclosed.

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?

A single front-loaded sentence with no filler; the verification action and the resulting account display are both stated up front. Nothing is wasted.

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?

With no annotations and no output schema, the description is the only source of return-value information, yet 'show the authenticated GitHub account' does not indicate which fields come back (login, name, email, scopes). For such a simple tool the omission is minor, but an agent cannot predict the response shape.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies the tool is argument-free by framing the token as 'configured' rather than passed in.

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?

States a specific verb pair (verify / show) against a specific resource (configured GitHub token, authenticated account). No sibling tool does authentication introspection, so the agent can immediately tell this is the identity/credential check rather than a repo or commit operation.

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?

Usage is only implied: 'verify the configured GitHub token' hints at a pre-flight credential check before other GitHub calls, but the description never says when to reach for it, nor does it reference any alternative or prerequisite. For a zero-param tool with no alternatives in the sibling list, this is adequate but not explicit.

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