sendDmNip44

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

The description says 'Send', implying an outgoing action, but does not disclose that the message is encrypted using NIP-44, that it creates a Nostr event, or what happens to the event after publishing. No annotations exist to compensate for this lack of transparency.

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 very concise, consisting of a single sentence. While it is front-loaded, it omits critical details such as encryption behavior and output, making it too terse to be fully effective.

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?

The description lacks explanation of encryption, return values, failure modes, and required setup (e.g., private key or bunker). For a tool with security implications and no output schema, this is insufficiently complete.

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 has 100% description coverage, so each parameter's purpose is already defined. The tool description adds no additional semantic value beyond what the schema provides, warranting the baseline score.

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 action 'Send' and the resource 'NIP-44 direct message', but does not explain how it differs from sibling tools like sendDmNip04 or encryptNip44. The name provides some differentiation but the description lacks explicit distinguishing details.

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?

No guidance is provided on when to use this tool over alternatives. There is no mention of encryption, comparison to sendDmNip04, or prerequisites like private key availability. The agent has to infer usage from the name and schema.

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