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. 'Look up' communicates a read-only, non-mutating operation, and 'Free' explicitly discloses a cost-related behavior. It does not detail error handling or authentication needs, but for a single-parameter lookup this is reasonably transparent.

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: 'Look up a DPYC community member by npub. Free.' The action and resource are front-loaded, and the additional sentence adds useful cost information without unnecessary detail.

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?

For a tool with one required parameter and an output schema, the description is enough to invoke it, especially since return values are presumably covered by the output schema. However, it omits context about what DPYC is, when this tool is preferable to related sibling tools, and how missing members are handled.

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 description names npub as the lookup key, which adds meaning to the single required parameter beyond the bare schema property name. However, it does not explain the npub format, where to obtain it, or any validation constraints, leaving the parameter semantics only minimally compensated.

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 clearly states the operation: look up a DPYC community member by npub, using the specific verb 'Look up' and a concrete resource. It does not explicitly distinguish itself from sibling tools like get_nostr_profile, but the member-by-npub scope is specific enough to be understood.

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 gives no guidance on when to use this tool versus related lookup tools, nor does it mention prerequisites such as having a valid npub or what to do if the member is not found. 'Free' hints at a cost consideration, but no alternatives or exclusions are provided.

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