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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read operation but does not explicitly state that it is read-only, nor does it describe pagination behavior, response format, or any side effects. The description adds minimal value beyond what the schema already states about parameters.

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 a single, concise sentence that front-loads the primary purpose and mentions filtering options. There is no redundancy or waste. It is optimal in length and structure.

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 tool with three optional parameters and no output schema, the description is adequate to convey the core action. However, it lacks any mention of the response format (though not required without an output schema) and does not provide routing guidance to alternatives, which could be considered a gap for a tool in a large ecosystem. Overall, it covers the basics but leaves room for improvement.

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?

The schema provides 100% coverage for parameter descriptions, so the baseline is 3. The description mentions 'filtering by country or worldwide availability' which loosely maps to the 'country' and 'worldwide' parameters, but it doesn't add any new semantic detail. The schema already explains that worldwide overrides country, so the description adds no additional clarity.

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 a clear action ('browse') and resource ('remote job listings'), with optional filtering mentioned. It is specific enough to convey the tool's core purpose, but it doesn't explicitly differentiate from sibling tools like search_jobs, which could serve a similar browsing need. The verb 'browse' suggests a listing vs. a search, but it's not explicit.

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 no guidance on when to use this tool versus alternatives. It does not mention that search_jobs might be better for complex queries or that get_job_details is for individual jobs. The agent is left to infer usage from the schema parameters alone, which is inadequate for distinguishing among siblings.

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