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

With no annotations, the description carries the safety/behavioral burden and does it thoroughly: it discloses cost, public visibility, attribution to the caller's npub, lack of verification, normal maintainer triage, and the not-configured failure mode. It also states return value shape, which is valuable for an agent deciding whether to call it.

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 front-loaded and well organized, with a one-line definition followed by purpose, consequences, and return behavior. A few phrases are slightly redundant ('Report it where the tool lives' restates the first sentence), but the length is justified by the fee/privacy/failure conditions.

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 5-parameter tool with a high-complexity auth token, the description plus schema covers purpose, prerequisites, side effects, costs, attribution, output, and failure behavior. The output schema is noted as present, and the description augments it with the concrete return fields (repo, number, url) and the not-charged condition.

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 100%, so the baseline applies. The description adds motivational context (why npub is required, why a fee exists) but does not add new syntactic or format details beyond the schema's already-detailed parameter documentation.

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 opening sentence names a specific action (file a field report), a resource (GitHub issue on the operator's repo), and a subject (this service). The follow-up question 'Found a tool's metadata or response wrong or confusing?' pins the exact use case and clearly separates it from the many service-operation siblings.

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 clearly signals when to use this tool: when a tool's metadata or response appears wrong or confusing. It does not explicitly enumerate when-not-to-use cases or name an alternative, but given this tool is unique among the siblings, the context is sufficient.

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