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

With no annotations, the description carries the full burden. It discloses that the event must be signed and gives character/fee constraints, but omits authentication requirements, publication side effects, error behavior, and what result the caller receives.

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 a single compact sentence with the core action front-loaded. It avoids unnecessary prose, though the fee/link clause is slightly cryptic.

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 mutation-oriented tool with a nested required object, no annotations, and no output schema, the description is too thin. It does not explain permissions, expected event structure beyond NIP-01, fee-tag placement, or return behavior.

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 50%, and the required event object has no field-level schema descriptions. The description adds meaningful semantics by specifying a signed NIP-01 event and referencing fee tags, but it does not explain the event object's required fields or fee-tag syntax.

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?

States a specific verb and resource: submitting a signed NIP-01 event. This is clearly more precise than the tool name alone, but it does not explicitly distinguish the tool from sibling posting/submission tools such as comment or submit_paper.

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 operational conditions about free posts, link counting, and fee tags, but gives no guidance on when to choose this tool over alternatives. No when-not-to-use or sibling routing is present.

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