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

Annotations already declare the tool is not read-only, not destructive, and idempotent. The description adds that conversation data is needed for reproduction, which is useful context, but it doesn't disclose side effects like where the report goes or if it triggers external actions. Given annotations, the description adds some value without contradiction.

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 concise and front-loaded, with two sentences that quickly communicate purpose and a key usage hint. Every sentence serves a purpose, making it efficient with no fluff.

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?

Despite having annotations and a simple schema, the description is too brief for a tool with three parameters. It doesn't explain the expected format of 'message' or 'context', nor what happens after submission. The tool's role in issue reporting is clear, but operational details are missing, making the description incomplete for effective use.

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 0%, so the description must compensate. It only hints at the 'conversation' parameter ('Include the conversation array') and leaves 'message' and 'context' unexplained. With three parameters and only one mentioned, the description fails to provide adequate meaning beyond what the schema already shows.

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's function: reporting bugs, missing features, or sending feedback, with a specific instruction to include conversation data. It distinguishes itself from sibling tools like authenticate or connect by focusing on issue reporting, though it doesn't explicitly name alternatives.

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 implies when to use the tool (when encountering a bug or giving feedback) but provides no explicit guidance on when not to use it or alternatives. It lacks exclusion criteria or prerequisites, leaving usage context mostly implied.

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