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

Adds real context beyond the annotations: signed-in account required, 10/day rate limit, and a 'no secrets' warning. The 'files an issue' phrasing is consistent with idempotentHint=false and openWorldHint=true. It stops short of saying what happens after submission (confirmation, issue link, duplicate behavior on repeat calls).

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?

Extremely tight — no wasted words, and the purpose is front-loaded ahead of constraints. The telegraphic fragments ('Signed-in account, 10/day. No secrets.') trade a little readability for density, but no sentence is filler.

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 2-parameter, non-destructive, annotation-covered tool this covers purpose, auth, quota, and a safety constraint. With no output schema, a brief note on what the caller gets back (issue number/URL) would close the remaining gap.

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% and both parameters (projectid, description) are documented in-schema, so the description adds little parameter-level meaning. It reinforces the 'No secrets' constraint, which is already present in the schema, so this is the baseline for fully covered params.

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 action (report a bug / request a component) and the concrete downstream side effect (files an issue on botkelp/components). This clearly separates it from every sibling, which are all get_/set_/search_ style tools.

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?

'Report a catalog/code bug or request a component' gives clear conditions for invoking it, which is well above the siblings' silence. It does not, however, exclude related cases (e.g. routing to get_help for a question rather than a bug), so the boundary with the help tool is left implicit.

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