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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=false, so the safety/mutation profile is covered. The description adds the crucial behavioral fact that this is a panel-driven telemetry sink rather than an assistant-callable action. It does not say what happens if an agent calls it anyway (error, silent write, discarded), which is the one remaining gap.

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?

Two short sentences, each earning its place: the first defines the tool and gives examples, the second delivers the decisive usage constraint without preamble.

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 non-agent-callable telemetry tool with no output schema, the description is complete enough: the agent's only needed decision is not to call it, and that is stated unambiguously. The undocumented parameters matter only to the panel code that calls this, though a one-line note on what happens on an unintended call would close the loop.

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 carry all meaning, but it only hints that 'event' takes action-like names (Run, Cancel) via examples. 'component' and the nested 'params' object are left entirely unexplained in both schema and description.

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 and resource ('record what the user did' in 'Desktop Commander panels') and gives concrete examples of the events ('pressing Run or Cancel'). The second sentence explicitly delimits who the caller is, so an agent can distinguish this from every sibling tool at a glance.

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?

Provides explicit when-not guidance: 'The assistant never calls this.' That is the strongest possible routing instruction and removes any ambiguity about whether an agent should invoke this among 30+ siblings.

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