Search Projects

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds that results are 'ordered newest-first,' which is valuable behavioral context beyond annotations. No contradictions.

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 well-structured with a clear purpose, args list, returns section, and use cases. It is concise, though some repetition exists (e.g., 'Number of results' in both description and schema). Overall, every sentence serves a purpose.

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?

Considering the 7 optional parameters, full annotations, and no output schema, the description adequately explains return fields (title, budget, bid count, skills) and ordering. It lacks error handling or pagination details, but these are covered by parameters. It is complete enough for typical use.

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 coverage is 100%, so baseline is 3. The description adds value by providing example keywords for the 'query' parameter, detailing budget descriptions ('in USD'), and including cross-tool guidance for the 'account' parameter (reference to freelancer_list_accounts).

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 'Search for projects/jobs on Freelancer.com by keyword, budget or project type,' which clearly defines the tool's action (search) and resource (projects). It distinguishes itself from siblings like freelancer_get_project (specific project) and freelancer_my_projects (user's own projects) by focusing on public search.

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 provides explicit example queries and use cases, such as 'Find projects for Zoho CRM' and 'Show me hourly WordPress jobs,' which guide when to use the tool. However, it does not explicitly mention when not to use it or how it differs from similar search tools like freelancer_search_skills.

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