Compatibility feedback action

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

Annotations supply readOnlyHint=false, openWorldHint=false and destructiveHint=true, so the safety profile is partly covered structurally, but the description adds nothing beyond them. Calling something that merely 'opens a page' destructive is an unexplained tension the description should have resolved (what state changes? what is destroyed?). With annotations present the bar is lower, but zero added context here.

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?

A single short sentence with no filler, and the alias framing is front-loaded. But the terseness shades into under-specification: the sentence is too small to carry the purpose, usage and parameter burden this tool has.

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?

With no output schema, two undocumented parameters, and a near-duplicate sibling, the description should be doing meaningful work; instead one sentence leaves the agent guessing about routing, parameter meaning, and the destructive side effect flagged by annotations.

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?

Two parameters at 0% schema description coverage, and the description says nothing about deviceId or deviceName. The names are self-descriptive, which keeps this above the floor, but the description makes no attempt to explain which device identifier matters or what happens if they are omitted (both are optional).

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 names a concrete action ('opens the Raccoon feedback page') and labels itself a 'compatibility alias', which hints at its relationship to give_feedback_to_raccoon. However, it never says what the feedback actually is or what the tool does with deviceId/deviceName, so the purpose stays only roughly sketched.

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?

There is a near-identical sibling, give_feedback_to_raccoon, and the description does not say when an agent should pick this alias over that one, nor whether both should be called. No prerequisites, no exclusions, no context about deprecation or preferred alternative.

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