Search the audit log

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds 'client-side substring filters' which hints at local filtering, but does not clarify performance implications or whether server-side filtering is also available. No contradiction with annotations.

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?

Single sentence, 10 words, no redundancy. Efficiently conveys core functionality.

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?

Description is minimal but covers the essence. With output schema present, return values are not needed. However, lacks note about client-side filtering potentially causing large data transfers, which is a important behavioral nuance for a search 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?

Schema provides descriptions for all 8 parameters (100% coverage). Description groups parameters into 'time range' and 'client-side substring filters', providing conceptual organization but no additional detail beyond 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?

Description specifies exact resource (/audit/events) and action (Search), and mentions specific filter types (time range, client-side substring). This is specific and distinct from sibling 'action1_list_audit_events' which likely lists without client-side filtering.

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?

Implies use for filtered audit log searches, but does not explicitly contrast with sibling 'action1_list_audit_events' or 'action1_search'. No when-not-to-use guidance provided.

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