jobs_recruitee_offer

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

No annotations provided, so description carries full burden. Clearly states 'Credential-free public ATS JSON', indicating no authentication needed. Also notes that structured compensation is returned only 'when the board exposes it', setting expectations about data availability. Does not cover rate limits or error handling, but the key behavioral traits are disclosed.

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?

Two sentences, highly concise. The first sentence is the action verb + resource, front-loaded. No redundant information. Every sentence adds value.

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?

No output schema, but description mentions return of 'full HTML/text description and structured compensation'. Provides context about data freshness ('when the board exposes it') and authentication. Lacks details on possible errors or missing data, but for a simple fetch tool, it is reasonably complete.

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 has 100% description coverage for both parameters (id and company). The description adds no additional parameter semantics beyond the schema's built-in descriptions. Baseline score of 3 is appropriate with high schema coverage.

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?

Description clearly states 'Get a single Recruitee offer', specifying the verb and resource. It distinguishes from the sibling 'jobs_recruitee_offers' (plural) by indicating a single offer. Mentions return details (description, compensation).

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?

Usage context is implied (fetch a specific offer by id and company subdomain), but there is no explicit guidance on when to use this tool versus alternatives like 'jobs_recruitee_offers' or other job board tools. No when-not-to-use or alternative suggestions.

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