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

With no annotations, description carries full burden. Discloses read-only nature, public data accessibility, and return behavior (latest fields or empty profile). Lacks information on rate limits or error handling, but is adequate for a simple read operation.

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, front-loaded with action, no redundant information. Every sentence adds value: what it does, why it's free, and what it returns.

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 single-parameter read tool with output schema, description covers key aspects: purpose, input, return shape, and behavioral note (public data). Could mention default behavior when npub is empty, but implied as 'empty profile'.

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?

Schema coverage is 0%; description clarifies that 'npub' parameter is the Nostr public key to look up. Does not specify format or validation, but provides sufficient context for intended use.

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?

Description explicitly states it reads a public Nostr profile for a given npub, distinguishing it from sibling write tool 'schwab_publish_nostr_profile'. Mentions specific metadata fields returned, making purpose precise.

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?

States tool is free and requires no proof because data is public, providing clear context for when to use. However, does not explicitly exclude alternative tools or provide when-not-to-use guidance beyond that.

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