nostr_delete_event

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

Discloses soft delete nature, relay honor uncertainty, and permission requirement. Without annotations, description carries burden and does well.

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?

Three sentences, each essential: purpose, behavior, prerequisite. No fluff, front-loaded.

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?

Adequate for a simple delete tool but lacks return value description. Output schema absent, so description could mention what response looks like.

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 covers both parameters completely; description adds minimal value (e.g., reason goes into content field). Baseline 3 given full schema coverage.

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?

Clearly states 'Publish a NIP-09 kind:5 deletion request', specifying verb, resource, and protocol standard. Differentiates from siblings like nostr_publish_event by focusing on deletion.

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 on soft deletion, relay behavior, and prerequisite (allowed kinds). Missing explicit when-not-to-use, but guides agent effectively.

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