source_recruitee

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

The description discloses that no authentication is required, which is a key behavioral trait. It also implies a read-only operation (fetch). Without annotations, this adds useful transparency, though it does not detail other behaviors like pagination or rate limits.

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, clear, and front-loaded sentence. Every word contributes to understanding the tool's function, with 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 the simplicity of the tool (single parameter, output schema exists), the description is complete enough for an agent to understand its purpose and basic usage. It does not elaborate on the output format, but the output schema covers that.

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?

Schema coverage is 100% and the parameter description is already provided in the input schema. The tool description does not add additional semantic meaning beyond what the schema provides, so baseline score 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 the purpose: fetching all open offers from a Recruitee company page. It specifies the platform (Recruitee) and the nature of the data (open offers), distinguishing it from sibling tools that target other sources.

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 when to use this tool (when you need open offers from Recruitee). It does not explicitly state when not to use or mention alternatives, but the sibling context makes it clear that this is for Recruitee-specific data.

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