announceSoftwareFromForgeRelease

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

With no annotations, the description carries the burden. It discloses auto-loading of .nostr-keys.json when privkey is omitted and specifies the event kinds (32267/30063/3063). However, it does not mention potential public write effects or reversibility, though 'announce' and 'catalog' imply a public write.

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 concise, information-dense sentences. Each sentence adds value: the action, the analogy to a known UI, and a key behavioral note. No redundant content.

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 an 11-parameter tool with no output schema, the description provides the core workflow and key behavioral context. It does not describe return values or edge cases, but the high schema coverage and clear purpose make it sufficiently complete for tool selection.

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 91%, so the schema already documents most parameters. The description adds only a note about privkey fallback which is also covered in the schema. It does not explain additional parameter semantics beyond what the schema provides, so baseline 3 is appropriate.

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 tool announces an Android app to a Zapstore/NIP-82 catalog from a forge Release APK, specifying event kinds and referencing the gittr Code sidebar action. This specific verb+resource combination distinguishes it from sibling tools like publishSoftwareAnnounce or publishRepoAnnouncement.

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 'Same as gittr Code sidebar Announce app' provides clear contextual usage, implying this tool replicates that UI action programmatically. It does not explicitly state when not to use it or name alternatives, but the source (forge Release APK) makes the intended scenario clear.

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