show_toast

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

Without annotations, the description implies a non-destructive action but provides no details on side effects, duration, or whether toasts can be dismissed. It is minimally sufficient for a simple notification but lacks depth.

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?

The description is a single sentence with no unnecessary words. It is concise and to the point.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the basic intent but misses details like message length limits or behavior when called multiple times. It is adequate for a straightforward tool.

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?

The single parameter 'message' has no schema description (0% coverage), and the tool description only paraphrases it as 'toast notification message'. No constraints like character limits or format are provided, adding little value beyond the schema.

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 action ('Display'), the object ('toast notification message'), and the context ('on the TV'). It uniquely identifies the tool among siblings, as no other tool deals with toasts.

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 'send_button' or other notification methods. There is no mention of prerequisites or context where toast notifications are appropriate.

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