qobrix_search_changes

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

No annotations are provided, so the description carries the full burden. It discloses the scope (tenant-wide, all records) and the endpoint, but does not explicitly state that this is a read-only operation, nor does it mention rate limits, permissions, or return format. This is not a contradiction but leaves some behavioral aspects undeclared.

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 five sentences, each earning its place: purpose, endpoint, use case, examples, and sibling pairing. It is front-loaded with the core functionality and avoids fluff.

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 six parameters, no output schema, and the sibling tool suite, the description covers purpose, scope, examples, and tool selection guidance. It lacks an explicit description of the response shape, but the fields parameter hints at return columns, so it is reasonably complete for an 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?

The schema description coverage is 100%, so the baseline is 3. The description reinforces the search examples but adds no new parameter semantics beyond what is already in the schema, which contains detailed descriptions for all six parameters.

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?

Specifically states it searches a tenant-wide audit log for a CRM resource, with the exact endpoint GET /api/v2/{resource}/changes. It also distinguishes from related sibling tools by pairing with qobrix_top_field_changers and qobrix_field_change_history.

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 says 'Use to find who changed what across all records' and provides search examples. It does not explicitly state when not to use, but the pairing guidance with alternatives gives clear selection context.

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