mac_fsevents_search

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

With no annotations, the description must disclose behavioral traits. It only states the tool searches and shows operations, omitting details such as performance implications, required permissions, or side effects. The schema provides some filtering context, but the description adds no extra transparency.

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 concise sentence, but it is too brief for a tool with 8 parameters. While not bloated, it sacrifices useful detail. A more structured description could improve clarity without adding length.

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 complexity (multiple filtering options, no output schema), the description is incomplete. It does not explain the return format, whether results are paginated, or how filtering interacts. The mention of event types gives a clue, but the overall context is insufficient for effective use.

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 75%, but the tool description adds no additional meaning to parameters. Two parameters (limit and offset) lack schema descriptions and are not explained in the text. The description only reiterates the general purpose without clarifying how parameters affect behavior.

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 tool searches FSEvents records for file system activity and lists specific event types (created, deleted, modified, renamed). This explicitly distinguishes it from siblings like mac_fsevents_stats or mac_investigate_event, which focus on statistics or deeper analysis.

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 is given on when to use this tool vs alternatives like mac_unified_logs_search or mac_spotlight_search. The description does not mention prerequisites, limitations, or exclusions.

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