publishBountyToNostr

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

The description only states 'Publish' without disclosing behavioral traits such as requiring a private key for signing, broadcasting to relays, or being a write operation. Since no annotations are provided, the agent lacks safety/behavioral context, which is critical for a tool with sensitive parameters like privkey.

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 extremely brief (one short sentence), but under-specification is not conciseness given the tool's complexity. With 13 parameters and no annotations, the description needs to convey much more context.

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?

This tool has a large parameter set, no output schema, and no annotations. The one-sentence description fails to explain the event structure, authentication requirements, return behavior, or any other contextual detail needed for correct usage. It is completely inadequate for a tool of this complexity.

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 description provides no information about any parameters. The input schema has 13 parameters but only one has a description (8% coverage), so the description fails to compensate for the schema's poor documentation. Key parameters like privkey, issueId, and amount are left unexplained.

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 explicitly states the action 'Publish' and the specific resource 'gittr bounty metadata event (kind 9806)', making it clear what the tool does. It distinguishes itself from sibling tools like publishRepoAnnouncement and publishRepoState by specifying the event kind.

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?

The description implies usage for publishing bounty metadata events via the event kind, which provides clear context. However, it doesn't explicitly mention alternatives or exclusions, but given the specificity, it's not misleading.

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