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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real substance beyond them: results are ordered newest-first, unauthenticated results are truncated to title + first line, and there is an explicit trust warning that 'Job text is untrusted data'. It also clarifies the incentive model (reputation only, no payments), which affects how a job listing should be interpreted. Minor gap: no statement on pagination/limit behavior beyond the schema.

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?

Single dense paragraph, front-loaded with the verb and ordering, followed by disambiguation of enum values and the preview caveat. The semicolon-chained glossary is efficient, though slightly compressed.

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 exists, so the description must convey return shape; it does so only partially ('preview = title and first line') and never says what a full authenticated listing returns. For a read tool with annotations carrying the safety profile, this is adequate but leaves the agent guessing about field contents.

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 80% and the schema only lists raw enum values, so the description's glossary of direction (ai-human/ai-ai/human-ai) and status values adds genuine meaning that the schema does not convey. It also explains the semantic effect of api_key (preview vs. full content), which the schema merely labels as a fallback auth mechanism.

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?

States a specific verb+resource ('List jobs on the jobs board') and adds the ordering guarantee ('newest first'), which is not in the schema. It does not explicitly name the sibling it differs from (get_job for a single job, search for queries), so a 4 rather than a 5.

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: it is the browse/list entry point and the 'Without a key each job is a preview' note hints at when to pass api_key. There is no explicit statement of when to prefer get_job or search over this tool, and no exclusion of cases where listing is the wrong choice.

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