Get recent account activity

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

Annotations already declare readOnlyHint: true, and the description's verb 'List' is consistent. No further behavioral details (e.g., rate limits, side effects) are needed given the read-only annotation. The description adds context about event types but does not go beyond annotation-covered behavior.

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?

Two sentences, front-loaded with the action and followed by usage and filter explanation. Very compact without missing key information; every sentence 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 simple read-only tool with two optional parameters and no output schema, the description covers purpose, usage, and filter semantics. No output format is described, but that is unnecessary given the absence of an output schema.

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?

Both parameters have full descriptions in the schema (kind with valid values, limit with default and max). The description's mention of 'kind filter' and example 'sign_in' is redundant with the schema, adding no new semantic information beyond what is already provided.

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?

Description states a specific action: 'List the user's most recent security + system audit events' and provides a clear usage trigger: 'Use this when the user asks "what happened recently" or "did anything change"'. This differentiates it from sibling tools like list_recommendations and get_savings_summary.

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 provides a when-to-use condition: 'Use this when the user asks...' but does not mention when to avoid or name alternative tools. The condition is clear and actionable, though it lacks explicit alternatives or negative guidance.

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