show_info_message

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

Without annotations, description provides basic behavior but lacks details about blocking nature, timeout, permissions, or whether it can be dismissed. Adequate but not rich.

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?

Single sentence, no redundancy, clearly conveys the main action. Could benefit from slightly more detail, but remains concise.

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 tool, description misses parameter clarifications and does not distinguish from similar siblings. Return behavior not mentioned, but output schema is absent so not fully required.

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?

With 0% schema description coverage, the description does not explain parameters beyond their names. It associates title and message with the informational page but omits the purpose of acknowledge_label.

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?

Clearly states it shows an informational page and waits for acknowledgement. Good verb+resource combination, but does not explicitly distinguish from sibling show_confirmation_dialog.

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?

No guidance on when to use this tool versus alternatives like show_confirmation_dialog or get_user_input. The description only states what it does, not when it's appropriate.

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