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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds the useful behavioral context that no token is needed, which is a meaningful disclosure. However, it doesn't describe what happens after feedback is submitted (e.g., confirmation, response format), and the annotations don't fully cover the behavioral profile. The 'no token needed' note is a genuine addition beyond annotations.

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?

Three short sentences with zero waste. The core purpose is front-loaded, the no-token note is a critical usage detail, and the category list is concise and useful. Every sentence 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 simple feedback tool with one required parameter and no output schema, the description is largely complete. It covers what to submit, useful categories, and the auth requirement (none). The only gap is the undocumented 'api_token' parameter, which is confusing given the 'no token needed' statement – the description could clarify why the parameter exists or that it can be ignored.

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. The description mentions 'message' implicitly (what's broken, confusing, missing, or working well) and 'category' explicitly (bug, idea, question, praise). However, it doesn't explain the 'api_token' parameter at all, and the description doesn't fully map to all three parameters. The category list in the description adds value beyond the schema, which has no enum values.

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 purpose: to tell the people running hashn what's broken, confusing, missing, or working well. It uses a specific verb ('tell') and resource ('people running hashn'), and it distinguishes itself from sibling tools by being the only feedback mechanism.

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 on when to use this tool (to report bugs, ideas, questions, praise) and explicitly notes that no token is needed, which is a useful usage guideline. It doesn't explicitly name alternatives or exclusions, but the sibling tools are all distinct operations (file management, workspace management, auth), so the usage context is clear.

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