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, but it only describes domain content rather than behavior. It does not say whether the tool is read-only, performs a network lookup, requires input, or how it behaves on invalid queries. The phrase 'linked social proofs' hints at output content but not at operational behavior.

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 very short, but this is under-specification rather than disciplined conciseness. Every word points to the tool's subject matter, yet none of it provides actionable guidance for selecting or invoking the tool.

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?

Although the tool has only one parameter and an output schema exists, the description is still incomplete because it fails to specify how 'q' maps to a Keybase identity or proof lookup. An agent would need to guess the input semantics and the intended use case, making correct invocation uncertain.

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 input schema has one optional parameter 'q' with a default value and 0% schema description coverage, but the description never explains what 'q' represents or what format is expected. An agent cannot determine whether 'q' should be a Keybase username, a fingerprint, a URL, or some other identifier.

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 identifies the resource domain (Keybase) and hints at the content (crypto identity and linked social proofs), but it lacks any verb or explicit action such as 'look up' or 'verify'. It is clearer than a pure tautology but does not fully tell an agent what operation the tool performs.

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 provides no guidance on when to use this tool versus alternatives. It does not state what input is expected, such as a username or identity query, nor does it mention any exclusions or related sibling tools. Usage must be inferred entirely from the tool name and description fragment.

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