sassy_audit_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Search audit log for a keyword' and does not mention output structure, pagination, how the 'count' parameter affects results, or any edge cases. This is minimal and under-specified.

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 with no fluff or repetition. It is front-loaded with the action and target resource. However, it is too sparse to fully support the tool's usage, but for conciseness alone it is well-structured.

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?

Although an output schema exists, the description is incomplete for a search tool. It fails to indicate how the 'count' parameter works, what the output entries look like, or how this search differs from other audit-related tools. The presence of many sibling tools increases the need for contextual differentiation, which is absent.

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 must compensate. It mentions 'keyword' which maps to the required parameter, but does not explain the 'count' parameter, its default value, or its effect on search results. The schema itself provides only a type and default without a description.

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 uses a specific verb 'Search' and resource 'audit log', clearly indicating the tool's function. It distinguishes from sibling tools like sassy_audit_log, sassy_audit_false_positives, and sassy_audit_clear by emphasizing a keyword-based search operation.

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?

There is no guidance on when to use this tool versus alternatives such as sassy_audit_log or sassy_audit_false_positives. No exclusions, prerequisites, or context are provided; the description only states the basic action.

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