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

The description goes far beyond the provided annotations by explicitly detailing the complex payment mechanism and the multi-step calling procedure. This provides critical behavioral context regarding transactional safety and resource management not found in structured data.

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 definition is dense due to necessary technical specifications (cost, payment workflow), but it is structured efficiently to deliver this complex information in a single, focused statement.

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?

While it explains how the search process works (payment flow, boards), it does not explicitly state the nature of the output, such as whether it returns a list of job objects or raw HTML/JSON, which is a key piece of contextual information missing when no output schema is provided.

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 input schema has 100% description coverage, making the baseline score 3. The description provides no additional semantic meaning for 'q', 'remote', 'source', or 'location' beyond what is already detailed in the schema.

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 tool's purpose is clearly stated as searching remote jobs across three public boards. It successfully differentiates its domain (jobs) from other potential search tools in the environment.

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 highly specific operational guidelines, detailing the cost ($0.005 per call) and the technical workflow required (the two-step process involving the PaymentRequired challenge and subsequent retry), which guides usage and cost management.

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