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

With no annotations provided, the description must disclose behavioral traits. It only says 'Search', which implies read-only, but does not explicitly state safety, return format, pagination, rate limits, or any side effects. This is insufficient for a tool with zero annotation coverage.

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 phrase with no unnecessary words. It is front-loaded and easy to parse, though it is arguably too minimal to be fully useful. Structure is clean, earning a 4.

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?

The tool has two optional parameters, no output schema, and no annotations. The description only states the basic function, leaving out parameter semantics, return value, and usage context. Given the complexity and lack of structured information, this is incomplete.

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 input schema has two parameters (query, pipelineId) with zero description coverage. The description adds no meaning to these parameters, failing to explain what query represents or how pipelineId filters results. The schema itself provides no descriptions, so the description must compensate but does not.

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 'Search CRM opportunities/deals' clearly identifies the action (search) and the resource (opportunities/deals). It distinguishes from sibling tools like search_contacts and search_conversations by specifying the target object.

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. It does not mention what kinds of searches are supported, whether to use this for deals vs opportunities, or when to use search_contacts or get_pipelines instead.

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