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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no indication of whether the query is keyword or natural-language, how many results return, whether auth or a referral code is required, or how 'exclusions and useful combinations' affect results. The one behavioral hint ('exclusions and useful combinations') is too vague to be actionable.

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?

It is a single short sentence with no waste, but its brevity stems from under-specification rather than tight writing, and the load-bearing phrase about exclusions/combinations is appended after the vague core instead of leading with concrete behavior.

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 2-parameter search tool with no annotations, no output schema, and 0% param coverage, the description should explain query semantics, result scope, and the referral_code requirement; it does none of these, leaving the agent guessing on every invocation detail.

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% and two parameters exist, so the description must compensate and does not. 'for a task' weakly hints that 'query' is a task description, but 'referral_code' (22-64 chars) is never explained and no format, syntax, or matching semantics are given for either parameter.

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 implies a search/lookup tool ('Find ... for a task') but the key resource is named in opaque jargon ('Mekler paid operations') rather than as services, and the trailing phrase 'including exclusions and useful combinations' muddies rather than clarifies what is returned. It is not a tautology, but an agent cannot confidently distinguish this from get_service or the referral_* siblings.

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 when-to-use statement, no prerequisite, and no mention of the alternative get_service for single-service retrieval. Nothing tells the agent when this search is preferable to the get_* tools.

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