get_recent_touch_events

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

No annotations provided, but description fully discloses behavior: pure read operation, privacy guarantee (no key contents, no clipboard targets, no scroll positions inside sensitive apps). Adds significant context beyond the schema.

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?

Well-structured with clear sections: function, return format, usage guidance, behavior, parameters. Every sentence adds value, no redundancy. Efficient and front-loaded.

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 simple single-parameter tool and presence of output schema, the description is complete. It explains the return data sufficiently and addresses privacy concerns, leaving no gaps for the agent.

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?

Parameter 'n' has no schema description (0% coverage), but the description adds meaning: 'number of events. Range 1-500. Default 50.' This compensates fully, providing constraints and defaults not in 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?

Clearly states the tool returns the most recent N keyboard and mouse activity events, with specific details on the returned data (timestamp, type, aggregate counts, active app). Distinguishes from siblings like get_touch_stats and get_activity_summary by focusing on event-level data.

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?

Explicitly states when to use (analyzing input patterns, idle detection, activity timing) and when not to use (keylogging). Provides a clear privacy guarantee, helping the agent avoid misuse.

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