android_notification_reply

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

The description adds a useful precondition (RemoteInput) that is not present in annotations. Annotations already signal mutation (readOnlyHint=false, destructiveHint=true, idempotentHint=false), so the description does not need to restate those. It does not disclose side effects such as whether the notification is dismissed or the reply is delivered, but the precondition is meaningful beyond structured data.

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 that states the operation and its key precondition without unnecessary words. Every part earns its place.

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 mutating tool with no output schema, the description is too sparse. It does not explain how to obtain the 'key', what happens after the reply is sent (e.g., notification dismissal), or what success/failure looks like. The sibling android_notifications likely provides the key, but this connection is not stated. An agent would need to make assumptions.

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 carries full responsibility for explaining parameters. It does not define 'key' or 'text', nor does it clarify that 'key' refers to a notification identifier and 'text' to the reply content. The tool name and description imply this mapping, but the description itself provides no explicit parameter semantics.

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 names a specific operation ('direct reply') and a specific resource ('a notification that exposes RemoteInput'), which clearly sets it apart from sibling tools like android_notification_open and android_notification_dismiss. An agent can immediately understand what action this tool performs and on what kind of target.

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?

The description explicitly states the precondition for use: the notification must expose RemoteInput. This gives the agent a clear condition to check before calling. However, it does not explicitly list alternatives or when not to use it, though the sibling set implies the distinction.

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