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

With no annotations provided, the description carries the full burden and does so well: it discloses that a small fee is charged (anti-abuse), that the report is PUBLIC and lands in maintainers' normal triage, that nothing is verified, that the npub is stamped as author of record, and the exact fallback behavior ("issue reporting not configured", no charge). These are real behavioral traits an agent needs before invoking.

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 purpose is front-loaded in the first sentence and each subsequent sentence adds a distinct fact (authorship, fee, publicness, return shape, fallback). It is slightly dense with parentheticals, but nothing is redundant.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the key return (repo, number, url) plus the non-configured outcome. Combined with the cost, attribution, and publicness disclosures, an agent has everything needed to invoke this external-write tool correctly.

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 100%, so the baseline is 3. The description reinforces the npub-as-author-of-record and proof requirements and adds the fee concept, but it does not add format or semantics for any parameter beyond what the schema already documents.

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 (file/report) and resource (a field report as a GitHub issue on the operator's repo), and the second paragraph makes the intended subject explicit (a tool's wrong or confusing metadata/response). No sibling tool covers this reporting function, so it is trivially distinguishable from the rest of the beesknees_* set.

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?

"Found a tool's metadata or response wrong or confusing? Report it where the tool lives" gives a clear triggering condition for use. It does not name an alternative or a when-not case, but there is no competing report tool to route against, so the only real gap is the absence of explicit exclusions.

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