get_remote_jobs

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only mentions the source and filtering capabilities but omits key behavioral traits such as caching behavior, rate limits, data freshness, or what happens with no results. The presence of a use_cache parameter is not explained in the description.

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?

Extremely concise at two sentences, front-loading the core purpose. No wasted words or extraneous details. Every sentence is meaningful.

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 simple job listing tool with four parameters and no output schema, the description covers the essential action. However, it lacks details on return format, ordering, pagination, and does not differentiate from similar tools, leaving gaps for an agent that needs to compare options.

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?

All four parameters are fully described in the schema (100% coverage), so the description adds little beyond reiterating filtering. It confirms that tags and search are used for filtering, which is already clear from schema descriptions. The baseline of 3 is appropriate.

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 that the tool retrieves remote job listings from RemoteOK with filtering by tags and keywords. However, it does not distinguish from the very similar sibling get_weworkremotely_jobs, limiting the clarity for an agent choosing between them.

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?

No guidance is given on when to use this tool versus alternatives like get_weworkremotely_jobs. There is no mention of prerequisites, when to filter vs search, or any context to help an agent decide to use this tool.

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