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

With no annotations provided, the description carries the full transparency burden, but it only adds the behavioral trait 'Free' and relies on the verb 'look up' to imply read-only behavior. It does not mention authentication, error behavior, side effects, or any other operational characteristic an agent might need.

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 extremely concise and front-loaded with the main purpose, followed by a short cost note. It contains no fluff or redundant wording and efficiently conveys the core action.

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 one-parameter tool with no annotations and the presence of an output schema, the definition misses important context: when to use this specific lookup tool versus the many similar siblings, expected behavior for unknown npubs, and format constraints. It is minimal but not complete enough for an uncertain agent.

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 provides no description for the 'npub' parameter (0% coverage), so the description is the only textual hint. Saying 'by npub' clarifies that npub is the search key, but it does not provide format, example, constraints, or how the value is interpreted, leaving an agent with incomplete information for building a valid request.

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 uses a specific verb ('Look up') and resource ('DPYC community member') and identifies the lookup key ('npub'). It clearly establishes what the tool does, but it does not differentiate this tool from siblings such as goodearth_get_nostr_profile or goodearth_list_canonical_identities.

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 offers no use-case guidance, conditions, prerequisites, or exclusions relative to the many sibling tools. It simply restates the tool's function without explaining when to choose it over alternatives.

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