Search freelancers

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

Annotations already cover read-only/idempotent safety, but the description adds real context beyond them: what a result card contains (score, average rating, review count), what 'rating' actually means (average employer score out of 5), and a negative capability disclosure ('The site has no city filter') that prevents a wasted geographic search. No pagination/limit behavior is restated, but that is fully in the schema.

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?

Three tight sentences: purpose and facets first, then the routing to sibling tools, then the disambiguation note on rating and the missing city filter. Every sentence earns its place with no repetition of schema fields.

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?

With 8 optional parameters, no output schema and full schema coverage, the description supplies what the structured fields cannot: what results look like and where to go for more depth. It does not mention the page/limit ceilings or result ordering edge cases, but those are adequately covered by the schema itself.

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 all eight parameters (including the sort enum, level enum, skills matching semantics and category slug sourcing) are already documented. The description adds only marginal semantics ('ranked by score' and the max-5 rating meaning), so baseline 3 applies.

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?

States a specific verb ('Search') plus resource ('Ponisha freelancers') and enumerates the searchable facets (text, skills, category, level, portfolio) with the ranking rule ('ranked by score'). It also disambiguates from siblings by naming pn_profile, pn_reviews and pn_portfolios as the tools that carry the deeper detail this one does not.

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?

'Use to find who to hire or to see who leads a niche' gives concrete selection contexts, and the follow-up routing sentence implicitly tells the agent when another tool is the better call. It stops short of an explicit when-not (e.g. when to prefer pn_search_projects or pn_services), so not quite a 5.

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