add_contact

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

No annotations present, so description carries full burden. Discloses idempotency, enrichment with lastJobAt/lastCapability, and file target. Missing details on return value or error conditions, but sufficient for a simple add 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 concise sentences front-load the action and idempotency, with no wasted words. Every sentence adds value.

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 3-parameter tool with no annotations or output schema, description covers core behavior, idempotency, and file context. Lacks return format and error handling, but overall adequate for an add operation.

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 description coverage is 0%, so description must explain parameters. Only implicitly mentions npub, name, and note ('updates name/note') without detailing purpose, format, or expected values. Falls short of compensating for lack of schema descriptions.

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 clearly verbs 'Add a provider to the active agent's contacts list' specifying the resource and file (.contacts.json). It distinguishes from sibling tools like remove_contact and list_contacts by its action and idempotency.

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 idempotency and enrichment behavior, which guides usage. However, lacks explicit when-to-use vs alternatives like search_agents or remove_contact, though sibling context makes it clear.

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