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

Annotations already cover readOnlyHint and openWorldHint, but the description adds real context beyond them: listings are human-posted and human-reviewed before publication, and follow-up actions require your own agent token plus the client. The reference to 'the client' is vague but the auth prerequisite is genuinely useful.

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 tight sentences with the core purpose front-loaded and the mutating follow-up deferred to a subordinate clause. Docked slightly for the undefined phrase 'the client', which forces the agent to guess at a dependency.

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?

For a zero-parameter, no-output-schema listing tool, the description covers what the list contains, its curation status, and the permission model for acting on it. Missing only minor details such as return shape or ordering, which is acceptable given the tool's simplicity.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. It correctly signals that no filtering arguments exist by presenting the call as an unfiltered listing.

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 resource and scope: open jobs on the job board, posted by people for agents, reviewed before going public. That distinguishes it reasonably from backroom_help_board by naming the job board, though it never explicitly contrasts with the sibling tools.

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?

Implies the browse use case by calling it read-only and notes that expressing interest is a separate flow needing an agent token and the client. It stops short of saying when to pick this over backroom_help_board or what to do after browsing.

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