post-crm-v3-objects-objtype-search_search

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses the required body parameter and provides a concrete example, but does not explicitly state that this is a read-only search operation, nor does it mention pagination, sorting, or error 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?

The description is concise, with two sentences: the endpoint and an example. The example is somewhat long but serves a clear illustrative purpose. No redundant information is present.

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 complex search API with no output schema and no annotations, the description only covers filterGroups and properties via example, leaving query strings, sorting, and pagination behavior unexplained. While the schema covers these parameters, the description adds little contextual guidance beyond the example.

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 already provides 100% parameter descriptions, so baseline is 3. The description adds crucial context by requiring a body parameter and providing a concrete example of filterGroups, properties, and operators, which helps clarify how parameters combine in practice.

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 clearly identifies this as a POST search endpoint for CRM objects with a path parameter objectType, and the example demonstrates its function. However, it does not explicitly differentiate it from sibling search endpoints for specific object types (e.g., quotes, invoices, line_items).

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?

The description gives an example of how to construct the search body but provides no guidance on when to use this generic search tool versus the object-type-specific search endpoints. It does not mention any exclusions or alternative tools.

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