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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the currency context (Haven Credits, 1,000 HC = $1), which is domain-relevant but does not disclose filtering defaults, sort order, or pagination behavior for this listing operation.

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 short sentences with the core purpose front-loaded and no filler or repetition. The currency sentence is efficiently worded, though it is only loosely related to invoking a job listing.

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 three-parameter filtered list tool with no output schema and thin schema descriptions, the definition should explain what a job record contains, what the default status filter is (the enum includes "all", leaving the default ambiguous), and how tag and limit behave. None of that is present, leaving real gaps an agent must guess at.

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 only 33%: "tag" is described circularly as "tag", and "limit" and "status" have no descriptions at all. The description supplies no meaning for any of the three parameters, so it does not compensate for the coverage gap beyond the self-explanatory status enum values.

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?

"Browse the job board" gives a clear verb (browse/list) and resource (jobs), and the sibling set makes it evident this is the collection-level read versus get_job for a single job or post_job/cancel_job for mutations. It falls short of 5 because it never names a sibling or states scope explicitly (e.g. all jobs vs. only open ones).

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_job for a specific job or list_bounties for a different board. The second sentence discusses currency denomination, which is not usage guidance at all.

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