source_smartrecruiters

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

No annotations are provided, so the description carries full burden. It mentions that the tool is read-only ('no auth required') and fetches 'all' postings, but does not disclose behavioral details such as pagination, rate limits, or potential performance implications. The safety profile is implicitly safe but not explicitly stated.

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, well-structured sentence that conveys all essential information: action, resource, source, and authentication requirement. No wasted words.

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 tool's simplicity (one parameter, no nested objects, output schema exists), the description provides adequate context for an agent to understand the tool's purpose and when to invoke it. The presence of an output schema reduces the need to describe return values. A slightly higher score could be justified but lacks any nuance about edge cases or limitations.

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 description coverage is 100% for the single parameter company_id. The description does not add additional meaning or usage context beyond what the schema already provides (the identifier format). Baseline 3 is appropriate since the schema already documents the parameter sufficiently.

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 tool fetches all public postings from the SmartRecruiters Posting API, with a specific verb ('Fetch') and resource ('public postings'). It distinguishes from sibling source tools by explicitly naming the source platform (SmartRecruiters) and noting no authentication is required.

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 the tool (when needing SmartRecruiters postings) and notes 'no auth required', but does not provide explicit when-not-to-use guidance or mention alternatives among the many sibling source tools. Usage context is clear but lacks exclusions.

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