nostr_publish_event

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

No annotations provided, but the description lists safety pipeline steps (read-only gate, signer presence, kind allowlist, rate limit, optional confirmation), disclosing behavioral traits.

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 that are front-loaded: first defines core function, second adds context. Every sentence earns its place.

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?

No output schema; description does not mention return value (e.g., event ID) or signing prerequisites. Missing some completeness for a primitive write tool.

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 100%, but the description adds value with examples for kind (common kinds), tag structure, content type, and created_at constraints.

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 it signs and broadcasts a raw NOSTR event of any allowed kind, and distinguishes itself as the primitive write tool with 'convenience wrappers around this'.

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?

Provides context that it's the primitive tool and mentions the safety pipeline, but does not explicitly state when to prefer convenience wrappers or when not to use it.

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