Notify the user

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

With no annotations, the description carries the full burden. It implies a transient, non-blocking UI display ('toast / quick message') but says nothing about whether the call waits for the user, what it returns, or how it behaves if Blockbench is unfocused. Key behavioral traits are left to inference.

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, front-loaded with what the tool does before how to use it. No filler, though the second sentence could be tightened.

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 three-parameter UI tool with no output schema, the description adequately conveys purpose and usage. However, in the absence of annotations and with zero parameter documentation, an agent still lacks the details needed to use icon/expire correctly.

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?

Three parameters with 0% schema description coverage: 'icon', 'expire', and 'text' are undocumented. 'Text' is inferable from 'toast / quick message', and 'quick' faintly hints at the auto-dismiss behavior of 'expire', but icon type and duration units/semantics are not addressed at all.

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 ('Show a toast / quick message inside Blockbench'), which is unambiguous. It does not explicitly contrast itself with siblings, but no sibling tool overlaps with user-facing notifications, so the intent is clear.

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?

Gives positive guidance on when to call it: to tell the human what the agent is doing, or to ask them to look at the screen. No when-not or alternatives are offered, but the use case is narrow enough that none are needed.

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