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

With no annotations provided, the description must disclose behavior. It only states a predicate about the existence of a GPG key, without mentioning whether it performs a read-only lookup, what it returns, or any input/output expectations. It does not contradict annotations because there are none, but it is insufficient.

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, which is succinct, but its brevity under-specifies the tool. The sentence is not tautological but fails to provide actionable detail, so it does not earn its place fully.

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?

While an output schema exists, the tool still requires a clear explanation of its input and purpose. The description is too sparse to allow correct invocation, especially given the ambiguous parameter. The tool's purpose is partially clear, but the lack of usage and parameter details leaves it incomplete.

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 has one parameter 'q' with no description and 0% schema coverage, so the description must explain it. The description does not mention 'q', what value should be passed (e.g., GitHub username), or any format. This is a critical 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 names the resource (GitHub GPG key) and a specific query (whether a user publishes one), but lacks an explicit verb like 'check' or 'retrieve'. It is vague enough that an agent might not immediately know the action to perform, though it is distinguishable from siblings like ghpubkeys by the GPG focus.

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 is provided on when to use this tool versus alternative GitHub query tools such as ghpubkeys or githubsearch. The description gives no context for selecting this tool.

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