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

With no annotations, the description carries the full behavioral burden, and it does add one genuinely useful trait: banners vanish after 5 s, mirroring a real heads-up notification. However, it never states that the tool is read-only, whether reading the shade dismisses or preserves the notifications, or what shape the results take, leaving significant behavioral questions for a stateful device tool.

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?

One compact sentence with the resource stated first and the notable 5-second expiry detail attached parenthetically. Nothing is wasted, though the sentence is a label rather than an action statement.

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 and no annotations, the description should clarify what the shade returns (message text? app source? timestamps?) and whether the list is cleared or persisted. The 5 s expiry hint is helpful but the return shape and side effects remain undefined for a one-parameter stateful 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?

There is a single required parameter, 'session', whose schema description ('Session from open_app') already fully documents it at 100% coverage. The description adds no extra meaning about the session scoping beyond repeating that notifications are per-session, so the baseline of 3 applies.

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 identifies the resource as 'the notification shade' holding notifications delivered to the simulated phone in this session, which implies a read/list of pending notifications. But it uses a noun phrase rather than a verb+resource and never distinguishes itself from the closely related siblings push_notification and open_notification, so an agent must infer which one surfaces vs. creates vs. opens a notification.

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 no statement of when to call this versus push_notification (which presumably creates one) or open_notification (which presumably taps one), nor any precondition such as requiring an open session. Usage is only implied by the noun phrase.

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