upwork_search_jobs

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

The description mentions it returns a list of job summaries with specific fields, which is helpful. However, with no annotations, it does not disclose pagination, result limits, or ordering behavior, leaving gaps for a search tool.

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 extremely concise at two sentences (27 words), front-loaded with the purpose, and contains no unnecessary information.

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?

Given full schema coverage and an existing output schema, the description provides sufficient context for a straightforward search tool. It covers purpose and return fields, though it lacks explicit usage hints for parameters.

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?

Input schema coverage is 100%, so baseline is 3. The description adds no additional meaning beyond what the schema already provides, such as parameter relationships or usage hints.

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 states 'Search for jobs on Upwork matching the specified criteria,' using a specific verb and resource. It distinguishes well from sibling tools like upwork_get_job_details, which retrieves details for a specific job.

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 implies its use for searching jobs but does not explicitly state when to use this tool versus alternatives. No guidance on exclusions or when not to use it is provided.

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