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

The description fully reveals behavior: returns specific metadata fields or an empty profile if none exists. Since no annotations exist, this description carries the full burden and does so thoroughly.

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?

Two sentences with no wasted words: first sentence defines the core action, second adds cost, authentication, and return details. Front-loaded and efficient.

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 the tool's simplicity (one optional param, no required fields, output schema exists), the description covers everything needed: the data source, public nature, return fields, and fallback behavior.

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?

With a single optional parameter and no schema description coverage, the description does not elaborate on the npub parameter beyond the tool name. However, the context makes it obvious; baseline 3 is appropriate.

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 'Read an npub's public Nostr profile (NIP-01 kind-0 metadata)', specifying the exact resource and action. It distinguishes from sibling tools like taxsort_publish_nostr_profile.

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 clear usage context: 'Free, no proof — the data is already public on relays.' This tells the agent no authentication is needed and it's safe to use, though it does not explicitly exclude other tools.

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