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

With no annotations, the description must disclose behavior itself. It only states the resource, not whether it fetches, lists, or does something else, nor any rate limits, authentication needs, or output structure. It is insufficient for a network-fetching 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 a single short sentence with no fluff, but it is under-specified. It doesn't front-load the most critical information like what the parameter means or the action performed. Conciseness is present, but structure and informativeness are lacking.

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 a single parameter and no output schema details, the description is incomplete. It fails to explain the input, the output format, or any constraints. For a tool that fetches from GitHub, it should at least mention the expected input (e.g., username) and that it returns a list of keys.

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 only parameter 'q' is not described at all, and the schema provides no description. The description doesn't explain what 'q' represents (likely a GitHub username or query). With 0% schema description coverage, the description should compensate but doesn't.

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 labels the tool as 'GitHub SSH Keys' and states it provides a user's public SSH keys, which gives a clear resource but lacks an explicit action verb like 'fetch' or 'list'. It distinguishes from siblings like ghkeysgpg (GPG keys) but could be more precise.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, typical scenarios, or when to prefer other GitHub-related tools (e.g., ghrepo, githubsearch). The agent must infer usage from the name alone.

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