listIssueComments

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does disclose the NIP-22 kind and root E tag relationship, and it clarifies that bounties are not changed, implying a read-only operation. But it does not mention pagination, relays behavior, or result format, leaving some transparency gaps.

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 two crisp sentences with no filler. The core purpose is front-loaded, and the bounty exclusion is a valuable, relevant clarification that 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?

For a straightforward list tool, the description conveys the essential filtering logic and scope. However, with no output schema, no annotations, and incomplete parameter documentation, an agent still faces meaningful gaps around available parameters and expected response details.

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 only 33%, with only issueId documented. The description adds minimal parameter meaning by explaining the issue id's role, but it says nothing about limit or relays, which the agent would have to infer from names and types.

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 states a specific verb and resource: 'List NIP-22 comments (kind 1111) on a Nostr issue'. It further clarifies the key technical detail (root E tag = issue id), which distinguishes it from related tools like listPRComments and listBountiesForIssue.

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 provides clear context by specifying this is for Nostr issue comments and explicitly excludes bounties. However, it does not name sibling alternatives like listPRComments or listBountiesForIssue directly, so the when-not guidance is implicit rather than fully explicit.

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