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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavior beyond annotations: AND semantics for criteria, pagination via offset/limit and next_offset, and the prerequisite to discover searchable fields via rex_describe_search_fields.

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 compact and front-loaded, starting with the core purpose and then covering filtering, paging, field discovery, and the endpoint. Every sentence carries useful operational context without unnecessary repetition.

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 nested criteria and order_by schema, the description supplies enough operational context to call the tool correctly, including AND filtering, pagination, and field discovery. It does not describe the returned campaign record structure beyond next_offset, which is a minor gap for a search tool without 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?

Schema description coverage is 100%, so the schema already documents limit, offset, criteria, order_by, and search_state in detail. The description reinforces filtering and pagination semantics but adds little parameter-level information beyond what the schema provides.

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 states a specific verb and resource: search campaigns, specifically nurture and marketing campaigns with their members. This clearly distinguishes it from the many other rex_search_* sibling tools by resource domain.

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?

It gives clear usage context by explaining that filters combine with AND and that paging uses offset/limit with next_offset. It also tells the agent to call rex_describe_search_fields with service Campaigns for searchable fields, but it does not explicitly state when not to use this tool versus alternatives.

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