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

With no annotations, the description carries the behavioral burden and delivers: it specifies that only 'currently open' jobs are returned, clarifies salary floor logic (compared against highest bound, posting's currency, no-pay roles never qualify), notes the default for omitted employment type, and mentions output URLs. This is substantive transparency, though it omits pagination/ordering details.

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 compact and front-loaded with the core purpose, then efficiently explains filters and output. No filler, every sentence earns its place.

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?

Without an output schema, the description covers query semantics and result fields (URLs). It does not mention pagination, ordering, result limits, or error cases, but for a listing tool the provided context is largely sufficient. Would be a 5 with pagination/ordering noted.

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%, so the schema already documents each parameter thoroughly. The description adds contextual reassurances ('same semantics as the site's jobs page', salary fields passed through) but does not introduce new meaning beyond the schema. This matches the baseline for 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?

The description uses a specific verb ('List') and a specific resource ('currently open DevRel job postings'), and enumerates the filters and output fields. This clearly distinguishes it from sibling tools like list_events (events) and search_directory (general directory search).

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?

It states that filters match the site's jobs page semantics, which implies when to use it (for job listings) and provides clear context. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of an explicit when/when-not/alternatives guide.

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